summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
| * Mark the dir-key-crosscert element as required.Nick Mathewson2013-11-14
| | | | | | | | This closes proposal 157.
* | Mark proposal 217 finished. Still needs merging into specNick Mathewson2013-11-14
| |
* | Mark proposal 146 superseded by 206Nick Mathewson2013-11-14
| |
* | Looks like Roger marked 213 as "should be marked Dead" without Deadening it. ↵Nick Mathewson2013-11-14
|/ | | | Deadening.
*-. Merge remote-tracking branches 'atagar/10086' and 'atagar/10085'Nick Mathewson2013-11-04
|\ \
| | * Don't enumerate event types in section 3.4Damian Johnson2013-11-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | When adding an event type we expect spec authors to edit both section 3.4 and 4.1.x. This is error prone... https://trac.torproject.org/10085 Dropping the redundant listing of event types and simply citing 4.1.x.
| * | Describing CONN_BW's ConnTypeDamian Johnson2013-11-03
| |/ | | | | | | | | | | | | | | | | | | Our new CONN_BW events' ConnType enumeration is poorly defined... https://trac.torproject.org/10086 This is just a guess on my part for what it's supposed to be. I have *not* trudged through the tor code to puzzle out how it actually allocates this enumeration.
* | Be an insufferable pedant and hyphenate a phrase.Nick Mathewson2013-11-04
| |
* | Fix a small mistake in pt-spec.txt.George Kadianakis2013-11-04
|/ | | | Fixes #10090.
* Document what we use for KH when we're doing ntor.Nick Mathewson2013-11-01
| | | | | | | | | | | | | | | | KH is part of the material derived from the KDF during the onion key process. In the TAP handshake, KH played two roles: it was sent by the server towards the client to prove that the server was able to complete the TAP handshake, AND it was included as part of the RELAY_ESTABLISH_INTRO message to make it impossible to replay a RELAY_ESTABLISH_INTRO from one circuit on another circuit. With the ntor handshake, the first value of KH was removed. But we still needed a shared, circuit-specific value for hidden service code to work. This value is taken as an additional 20 bytes from the KDF. It wasn't documented in the spec, though. Adding it here.
* reindex proposalsNick Mathewson2013-11-01
|
* Merge proposal 221 (stop using CREATE_FAST)Nick Mathewson2013-10-31
|
* Merge implemented proposal 218 into control-spec.txt.Karsten Loesing2013-10-31
|
* Rename DUMP->DROP, add a warningNick Mathewson2013-10-25
|
* add DUMPGUARDS commandr.a@posteo.net2013-10-25
|
* Update proposal index with 222 closedNick Mathewson2013-09-20
|
* Merge branch 'implement_prop222'Nick Mathewson2013-09-20
|\
| * Merge proposal 222 (eliminate timestamps) into the specificationsNick Mathewson2013-09-18
| | | | | | | | Also update it with actual decisions and parameters.
* | Fix typo.Linus Nordberg2013-09-19
|/
* Merge branch 'bug8929_take2_squashed'Nick Mathewson2013-09-07
|\
| * Split "Server behavior" section into smaller sections.George Kadianakis2013-09-07
| |
| * Specify how to pass configuration parameters to server transports.George Kadianakis2013-09-07
|/ | | | Also, add an example of the SOCKS parameters.
* Whoops; add 222 to the index.Nick Mathewson2013-09-07
|
* Small clarification on the TRANSPORT_LAUNCHED control event.George Kadianakis2013-08-26
| | | | Spec confusion pointed out by atagar in #9588.
* Merge remote-tracking branch 'asn/bug7317'Nick Mathewson2013-08-25
|\
| * Add TRANSPORT_LAUNCHED control port event.George Kadianakis2012-11-04
| |
* | Proposal 222-remove-client-timestampsNick Mathewson2013-08-22
| |
* | Merge branch 'bug8045_take3_squashed'Nick Mathewson2013-08-15
|\ \
| * | Introduce the "bridge-transports" extra-info descriptor field.George Kadianakis2013-08-15
| | |
* | | Merge branch 'bug7751_take2_squashed'Nick Mathewson2013-08-15
|\ \ \
| * | | Add descriptions for the commands of the Extended ORPort.George Kadianakis2013-08-15
| | | |
| * | | Pass name of transport to the Extended ORPort.George Kadianakis2012-12-24
| | |/ | |/|
* | | 220-ecc-id-keys: fix gaps noted by Sebastian GNick Mathewson2013-08-13
| | |
* | | Merge remote-tracking branch 'asn/bug8978'Nick Mathewson2013-08-13
|\ \ \
| * | | Specification on how the 'transport' extra-info line works.George Kadianakis2013-07-02
| | | | | | | | | | | | | | | | | | | | | | | | Also specify how pluggable transport arguments are passed from the transport proxy to Tor and then to the bridge authority using extra-info descriptors.
* | | | Fix a logic error; found by Ian Goldberg.Nick Mathewson2013-08-12
| | | |
* | | | Add an Ed25519 identities proposal and a kill-create_fast proposalNick Mathewson2013-08-12
| | | |
* | | | Tweak 219 a little moreNick Mathewson2013-08-12
| | | |
* | | | 219-expanded-dns: include some XXs from OndrejNick Mathewson2013-08-12
| | | |
* | | | 219-expanded-dns: finish my editsNick Mathewson2013-08-12
| | | | | | | | | | | | | | | | | | | | These are mainly about how to normalize requests and responses, plus a few security notes.
* | | | 219-expanded-dns: Clarify the exact packet format.Nick Mathewson2013-08-12
| | | | | | | | | | | | | | | | | | | | Also, make it a bit more extensible, in case we do get multi-packet responses working in the future.
* | | | 219-expanded-dns: Isolate the references to DNSSECNick Mathewson2013-08-12
| | | | | | | | | | | | | | | | | | | | | | | | This was originally a DNSSEC proposal, but the round trip issue makes it look as though this proposal is not sufficient to implement DNSSEC for practical use.
* | | | Add Ondrej's dns proposal in its original formNick Mathewson2013-08-12
| | | |
* | | | List link protocol versions 3 and 4 in description of VERSIONSNick Mathewson2013-08-12
| | | |
* | | | Noting maximum number of fingerprints/hashes that can be queriedDamian Johnson2013-07-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In our tor-dev@ discussion Karsten mentioned that we could request at most 96 descriptors at a time when polling by their fingerprints... https://lists.torproject.org/pipermail/tor-dev/2013-June/005005.html This is a hardcoded limit in tor, so noting it in our spec... https://gitweb.torproject.org/tor.git/blob/HEAD:/src/or/routerlist.c#l4435
* | | | Removing '/tor/micro/all' from the dir-specDamian Johnson2013-07-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The dir-spec describes a dirport method for retrieving all microdescriptors. While this is a fine idea it was never implemented. Moving the spec portion that describes this to the attic for now. https://trac.torproject.org/9271
* | | | Noting that GETINFO ns/* options provide v3 directory informationDamian Johnson2013-06-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Tor moved from v2 to v3 directory information in commit 3ad6dc0e. Prior to that Tor's 'GETINFO ns/*' options provided v2 information, but since then it's been v3. For more information see... https://trac.torproject.org/7953 Technically this is a tor bug, but it happens to be a convenient one so simply updating our spec. In practice controller authors haven't noticed this discrepancy because v3 router status entries are a superset of the fields in v2.
* | | | Add three older documents removed from tor.gitNick Mathewson2013-06-12
|/ / /
* | | Revert a little bit of that last change; put #6872 to bed.Nick Mathewson2013-05-22
| | |
* | | Allowing for new 'bandwidth-weights' entriesDamian Johnson2013-05-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Mike has expressed on ticket #6872 and irc that he based bandwidth-weights after the 'params' entry and would like new bandwidth-weights to be permitted. Changing the spec as follows... - Allowing for unspecified new 'Keyword=Int32' pairs, keeping the 'params' requrement that they're sorted. - Making all values optional, including the current ones. This is a change, but will give Mike greater flexability and avoid creating a headache of 'these weights are mandatory in consensus-method X and these other are mandatory in consensus-method Y'.
generated by cgit v1.2.1 (git 2.18.0) at 2024-02-08 07:45:25 +0000