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

[weasel]

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

[nickm]

I'd take a patch for this.

[nickm]

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

[cypherpunks]

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.

[arma]

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