aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2017-05-26 15:45:39 -0400
committerRoger Dingledine <arma@torproject.org>2017-05-30 14:15:42 -0400
commit5860f0a7c8ec6aa9eb542a86b828f69e20251c98 (patch)
tree45174c905b4371c3ef3eebf2ed85a44c09e33d77 /doc
parent4a15b3169645a397fc8193f91737604538ac077e (diff)
downloadtor-5860f0a7c8ec6aa9eb542a86b828f69e20251c98.tar.gz
tor-5860f0a7c8ec6aa9eb542a86b828f69e20251c98.zip
Update the torify.1 manpage
I went into this to fix 6892 and say "we don't do anything for circuit isolation." But instead I did a fair amount of text-removal to stop implying that torify does anything more than call torsocks.
Diffstat (limited to 'doc')
-rw-r--r--doc/torify.1.txt22
1 files changed, 11 insertions, 11 deletions
diff --git a/doc/torify.1.txt b/doc/torify.1.txt
index 8dca901317..614e3f63fb 100644
--- a/doc/torify.1.txt
+++ b/doc/torify.1.txt
@@ -17,25 +17,25 @@ SYNOPSIS
DESCRIPTION
-----------
-**torify** is a simple wrapper that attempts to find the best underlying Tor
-wrapper available on a system. It calls torsocks with a tor specific
-configuration file. +
+**torify** is a simple wrapper that
+calls torsocks with a tor-specific
+configuration file.
-torsocks is an improved wrapper that explicitly rejects UDP, safely resolves DNS
-lookups and properly socksifies your TCP connections. +
-
-Please note that since both method use LD_PRELOAD, torify cannot be applied to
-suid binaries.
+It is provided for backward compatibility; probably instead you should
+just use torsocks.
WARNING
-------
-When used with torsocks, torify should not leak DNS requests or UDP data. +
+When used with torsocks, torify should not leak DNS requests or UDP data.
+
+torify can leak ICMP data.
-Both will leak ICMP data.
+torify will not ensure that different requests are processed on
+different circuits.
SEE ALSO
--------
-**tor**(1), **tor-resolve**(1), **torsocks**(1)
+**tor**(1), **torsocks**(1)
AUTHORS
-------