Opened 7 years ago
Closed 3 years ago
#6892 closed defect (implemented)
improve torify manpage to say different connections may be over the same circuit.
Reported by: | weasel | Owned by: | dgoulet |
---|---|---|---|
Priority: | Medium | Milestone: | Tor: 0.3.1.x-final |
Component: | Core Tor/Tor | Version: | Tor: 0.2.3.21-rc |
Severity: | Normal | Keywords: | tor-client documentation |
Cc: | Actual Points: | 0 | |
Parent ID: | Points: | ||
Reviewer: | Sponsor: |
Description
Linus Lüssing would like the torify manpage to spell out that it does not do anything to make different torify calls unlinkable.
Probably not an unreasonable request.
For details of his request see
http://bugs.debian.org/681123
Cheers,
weasel
Child Tickets
Change History (9)
comment:1 Changed 7 years ago by
Milestone: | → Tor: 0.2.3.x-final |
---|
comment:2 Changed 7 years ago by
Keywords: | tor-client added |
---|
comment:3 Changed 7 years ago by
Component: | Tor Client → Tor |
---|
comment:4 Changed 7 years ago by
Milestone: | Tor: 0.2.3.x-final → Tor: unspecified |
---|
comment:5 Changed 3 years ago by
Component: | Core Tor/Tor → Core Tor/Torsocks |
---|---|
Owner: | set to dgoulet |
Severity: | → Normal |
comment:6 Changed 3 years ago by
Milestone: | Tor: unspecified |
---|
comment:7 Changed 3 years ago by
Actual Points: | → 0 |
---|---|
Component: | Core Tor/Torsocks → Core Tor/Tor |
Keywords: | documentation added |
Milestone: | → Tor: 0.3.1.x-final |
Status: | new → needs_review |
Wait, no, this did belong in Tor.
I've written a tiny patch as torify-manpage
that also removes some legacy text from torify.1.txt
comment:8 Changed 3 years ago by
Drive-by cypherpunks with some small improvements.
diff --git a/doc/torify.1.txt b/doc/torify.1.txt index 614e3f63f..f0f665437 100644 --- a/doc/torify.1.txt +++ b/doc/torify.1.txt @@ -17,12 +17,10 @@ SYNOPSIS DESCRIPTION ----------- -**torify** is a simple wrapper that -calls torsocks with a tor-specific +**torify** is a simple wrapper that calls torsocks with a tor-specific configuration file. -It is provided for backward compatibility; probably instead you should -just use torsocks. +It is provided for backward compatibility; instead you should use torsocks. WARNING ------- @@ -30,8 +28,8 @@ When used with torsocks, torify should not leak DNS requests or UDP data. torify can leak ICMP data. -torify will not ensure that different requests are processed on -different circuits. +torify will not ensure that different requests are processed on different +circuits. SEE ALSO -------- @@ -39,4 +37,4 @@ SEE ALSO AUTHORS ------- -Peter Palfrader and Jacob Appelbaum wrote this manual. +Written by Peter Palfrader and Jacob Appelbaum.
comment:9 Changed 3 years ago by
Resolution: | → implemented |
---|---|
Status: | needs_review → closed |
Merged. I took some of the suggestions from cypherpunks above (but not all of them, because some of them were mistaken). Thanks!
Note: See
TracTickets for help on using
tickets.
I'd take a patch for this.