mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-20 02:09:24 +01:00
5860f0a7c8
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.
43 lines
948 B
Plaintext
43 lines
948 B
Plaintext
// Copyright (c) The Tor Project, Inc.
|
|
// See LICENSE for licensing information
|
|
// This is an asciidoc file used to generate the manpage/html reference.
|
|
// Learn asciidoc on http://www.methods.co.nz/asciidoc/userguide.html
|
|
:man source: Tor
|
|
:man manual: Tor Manual
|
|
torify(1)
|
|
=========
|
|
|
|
NAME
|
|
----
|
|
torify - wrapper for torsocks and tor
|
|
|
|
SYNOPSIS
|
|
--------
|
|
**torify** __application__ [__application's__ __arguments__]
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
**torify** is a simple wrapper that
|
|
calls torsocks with a tor-specific
|
|
configuration file.
|
|
|
|
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.
|
|
|
|
torify can leak ICMP data.
|
|
|
|
torify will not ensure that different requests are processed on
|
|
different circuits.
|
|
|
|
SEE ALSO
|
|
--------
|
|
**tor**(1), **torsocks**(1)
|
|
|
|
AUTHORS
|
|
-------
|
|
Peter Palfrader and Jacob Appelbaum wrote this manual.
|