tor/contrib/torify.1

43 lines
1.4 KiB
Groff
Raw Normal View History

.TH torify 1 "" Jan-2009 ""
.\" manual page by Peter Palfrader and Jacob Appelbaum
2004-02-17 01:46:59 +01:00
.SH NAME
.LP
torify \- wrapper for torsocks or tsocks and tor
2004-02-17 01:46:59 +01:00
.SH SYNOPSIS
\fBtorify\fP\ \fIapplication\fP\ [\fIapplication's\ arguments\fP]
.SH DESCRIPTION
\fBtorify\fR is a simple wrapper that attempts to find the best underlying Tor
wrapper available on a system. It calls torsocks or tsocks with a tor specific
2004-02-17 01:46:59 +01:00
configuration file.
torsocks is an improved wrapper that explictly rejects UDP, safely resolves DNS
lookups and properly socksifies your TCP connections.
tsocks itself is a wrapper between the tsocks library and the application
2004-09-27 03:28:17 +02:00
that you would like to run socksified.
2004-02-17 01:46:59 +01:00
Please note that since both method use LD_PRELOAD, torify cannot be applied
2004-09-27 03:28:17 +02:00
to suid binaries.
2004-02-17 01:46:59 +01:00
.SH WARNING
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
2009-01-18 02:08:48 +01:00
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.
When used with torsocks, torify should not leak DNS requests or UDP data.
Both will leak ICMP data.
2004-02-17 01:46:59 +01:00
.SH SEE ALSO
.BR tor (1),
2009-01-18 02:08:48 +01:00
.BR tor-resolve (1),
.BR torsocks (1),
2004-02-17 01:46:59 +01:00
.BR tsocks (1),
.BR tsocks.conf (5).