diff options
| author | Peter Palfrader <peter@palfrader.org> | 2009-01-18 01:08:48 +0000 |
|---|---|---|
| committer | Peter Palfrader <peter@palfrader.org> | 2009-01-18 01:08:48 +0000 |
| commit | d21d90c9b96b68ca4975cbec905b7001023588e1 (patch) | |
| tree | 751d33f87a9aebd3512690c69ef3aaae06653bc7 /contrib | |
| parent | 0d77226a194c5f50d3e441bf646059f858b0cb67 (diff) | |
| download | tor-d21d90c9b96b68ca4975cbec905b7001023588e1.tar.gz tor-d21d90c9b96b68ca4975cbec905b7001023588e1.zip | |
Mention tor-resolve also
svn:r18162
Diffstat (limited to 'contrib')
| -rw-r--r-- | contrib/torify.1 | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/contrib/torify.1 b/contrib/torify.1 index d3059e90d5..b08d468451 100644 --- a/contrib/torify.1 +++ b/contrib/torify.1 @@ -20,11 +20,13 @@ 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 +normal system resolver to your usual resolving nameservers. The +\fBtor-resolve\fR(1) tool can be useful as a workaround in some cases. +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 tor-resolve (1), .BR tsocks (1), .BR tsocks.conf (5). |