improve torify manpage to say different connections may be over the same circuit.

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

changed milestone to %Tor: 0.3.1.x-final in legacy/trac

added actualpoints::0 in Legacy / Trac component::core tor/tor in Legacy / Trac documentation in Legacy / Trac milestone::Tor: 0.3.1.x-final in Legacy / Trac owner::dgoulet in Legacy / Trac priority::medium in Legacy / Trac resolution::implemented in Legacy / Trac severity::normal in Legacy / Trac status::closed in Legacy / Trac tor-client in Legacy / Trac type::defect in Legacy / Trac version::tor 0.2.3.21-rc in Legacy / Trac labels

I'd take a patch for this.

Trac:
Milestone: N/A to Tor: 0.2.3.x-final

Trac:
Keywords: N/A deleted, tor-client added

Trac:
Component: Tor Client to Tor

Trac:
Milestone: Tor: 0.2.3.x-final to Tor: unspecified

Trac:
Component: Core Tor/Tor to Core Tor/Torsocks
Owner: N/A to dgoulet
Sponsor: N/A to N/A
Severity: N/A to Normal
Reviewer: N/A to N/A

Trac:
Milestone: Tor: unspecified to N/A

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

Trac:
Status: new to needs_review
Component: Core Tor/Torsocks to Core Tor/Tor
Actualpoints: N/A to 0
Milestone: N/A to Tor: 0.3.1.x-final
Keywords: tor-client deleted, tor-client documentation added

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.

Merged. I took some of the suggestions from cypherpunks above (but not all of them, because some of them were mistaken). Thanks!

Trac:
Resolution: N/A to implemented
Status: needs_review to closed

closed

moved from legacy/trac#6892 (moved)

added Bug label and removed 1 deleted label

added Client + 1 deleted label and removed 1 deleted label

added Documentation label and removed 1 deleted label