ntor is not documented in tor-spec.txt, dir-spec.txt
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Robert Ransom changed milestone to %Tor: 0.2.4.x-final
changed milestone to %Tor: 0.2.4.x-final
Bulk-replacing "spec" and "torspec" keywords with "tor-spec".
Trac:
Keywords: spec deleted, tor-spec addedTrac:
Milestone: N/A to Tor: 0.2.4.x-finalTrac:
Summary: ntor is not documented in tor-spec.txt to ntor is not documented in tor-spec.txt, dir-spec.txt
Owner: N/A to nickm
Status: new to acceptedPlease somebody skim branch "document-ntor" in my public torspec repository.
Trac:
Status: accepted to needs_review- Author
Did you really use the same command number for both
CREATE2
andCREATED2
? - Author
+ In general, clients SHOULD use CREATE whenever they are using the TAP + handshake, and CREATED2 otherwise. Clients SHOULD NOT send the
s/CREATED2/CREATE2/
+ Servers always replay to a successful reply CREATE with a CREATED,
s/reply //
s/replay/reply/
Trac:
Status: needs_review to needs_revision - Author
+ When used in the ntor handshake, the first HASH_LEN form the forward
s/HASH_LEN/& bytes/
Thanks for the review, rransom!
Did you really use the same command number for both CREATE2 and CREATED2?
Ha; that would be some tricky engineering if I had! In fact, I just copy-and-pasted a number wrongly.
This and the other fixes above are now in branch "more-specs." Thanks!
Trac:
Status: needs_revision to needs_reviewMerged; thanks!
Trac:
Resolution: N/A to implemented
Status: needs_review to closed- Trac closed
closed
- Trac moved to tpo/core/tor#8122 (closed)
moved to tpo/core/tor#8122 (closed)