torify.1.txt 1.6 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950
  1. // Copyright (c) The Tor Project, Inc.
  2. // See LICENSE for licensing information
  3. // This is an asciidoc file used to generate the manpage/html reference.
  4. // Learn asciidoc on http://www.methods.co.nz/asciidoc/userguide.html
  5. torify(1)
  6. =========
  7. Peter Palfrader
  8. Jacob Appelbaum
  9. NAME
  10. ----
  11. torify - wrapper for torsocks or tsocks and tor
  12. SYNOPSIS
  13. --------
  14. **torify** __application__ [__application's__ __arguments__]
  15. DESCRIPTION
  16. -----------
  17. **torify** is a simple wrapper that attempts to find the best underlying Tor
  18. wrapper available on a system. It calls torsocks or tsocks with a tor specific
  19. configuration file. +
  20. torsocks is an improved wrapper that explictly rejects UDP, safely resolves DNS
  21. lookups and properly socksifies your TCP connections. +
  22. tsocks itself is a wrapper between the tsocks library and the application that
  23. you would like to run socksified. +
  24. Please note that since both method use LD_PRELOAD, torify cannot be applied to
  25. suid binaries.
  26. WARNING
  27. -------
  28. You should also be aware that the way tsocks currently works only TCP
  29. connections are socksified. Be aware that this will in most circumstances not
  30. include hostname lookups which would still be routed through your normal system
  31. resolver to your usual resolving nameservers. The **tor-resolve**(1) tool can be
  32. useful as a workaround in some cases. The Tor FAQ at
  33. https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ might have further
  34. information on this subject. +
  35. When used with torsocks, torify should not leak DNS requests or UDP data. +
  36. Both will leak ICMP data.
  37. SEE ALSO
  38. --------
  39. **tor**(1), **tor-resolve**(1), **torsocks**(1), **tsocks**(1),
  40. **tsocks.conf**(5).