diff options
author | Peter Palfrader <peter@palfrader.org> | 2009-01-18 01:05:17 +0000 |
---|---|---|
committer | Peter Palfrader <peter@palfrader.org> | 2009-01-18 01:05:17 +0000 |
commit | 0636369b83f9a31dc9324ee10f1a3d20e290c963 (patch) | |
tree | 407244fa7d24b6ae0259db3330f789007bff83d6 /contrib/torify.1 | |
parent | 58110054427a74075c28e78345005ad9546b612c (diff) | |
download | tor-0636369b83f9a31dc9324ee10f1a3d20e290c963.tar tor-0636369b83f9a31dc9324ee10f1a3d20e290c963.tar.gz |
mention that tsocks only socksifies TCP
In the torify(1) manpage explain that tsocks will only socksify
TCP connections, and that therefore it will most likely leak DNS
requests.
svn:r18160
Diffstat (limited to 'contrib/torify.1')
-rw-r--r-- | contrib/torify.1 | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/contrib/torify.1 b/contrib/torify.1 index cb9f01cfd..d3059e90d 100644 --- a/contrib/torify.1 +++ b/contrib/torify.1 @@ -1,4 +1,4 @@ -.TH torify 1 "" Feb-2004 "" +.TH torify 1 "" Jan-2009 "" .\" manual page by Peter Palfrader .SH NAME .LP @@ -17,6 +17,13 @@ that you would like to run socksified. Please note that since tsocks uses LD_PRELOAD, torify cannot be applied to suid binaries. +You should also be aware that the way tsocks currently works only TCP +connections are socksified. Be aware that this will in most circumstances +not include hostname lookups which would still be routed through your +normal system resolver to your usual resolving nameservers. The Tor +FAQ at https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ might +have further information on this subject. + .SH SEE ALSO .BR tor (1), .BR tsocks (1), |