Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Tor
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Container Registry
Model registry
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
The Tor Project
Core
Tor
Commits
59a9908f
Commit
59a9908f
authored
15 years ago
by
Sebastian Hahn
Browse files
Options
Downloads
Patches
Plain Diff
Convert the torify manpage to asciidoc
parent
2fc0c303
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
4
Hide whitespace changes
Inline
Side-by-side
Showing
4 changed files
.gitignore
+4
-0
4 additions, 0 deletions
.gitignore
doc/Makefile.am
+7
-3
7 additions, 3 deletions
doc/Makefile.am
doc/torify.1
+0
-42
0 additions, 42 deletions
doc/torify.1
doc/torify.1.txt
+50
-0
50 additions, 0 deletions
doc/torify.1.txt
with
61 additions
and
45 deletions
.gitignore
+
4
−
0
View file @
59a9908f
...
...
@@ -97,6 +97,10 @@
/doc/tor-gencert.1.in
/doc/tor-gencert.html
/doc/tor-gencert.html.in
/doc/torify.1
/doc/torify.1.in
/doc/torify.html
/doc/torify.html.in
# /doc/design-paper/
/doc/design-paper/Makefile
...
...
This diff is collapsed.
Click to expand it.
doc/Makefile.am
+
7
−
3
View file @
59a9908f
asciidoc_files
=
tor-gencert
asciidoc_files
=
tor-gencert
torify
html_in
=
$(
asciidoc_files:
=
.html.in
)
...
...
@@ -8,9 +8,9 @@ EXTRA_DIST = HACKING \
tor-resolve.1
\
$(
html_in
)
$(
man_in
)
$(
asciidoc_files:
=
.1.txt
)
\
tor-osx-dmg-creation.txt tor-rpm-creation.txt
\
tor-win32-mingw-creation.txt
torify.1
tor-win32-mingw-creation.txt
nodist_man_MANS
=
tor.1 tor-resolve.1
torify.1
$(
asciidoc_files:
=
.1
)
nodist_man_MANS
=
tor.1 tor-resolve.1
$(
asciidoc_files:
=
.1
)
doc_DATA
=
$(
asciidoc_files:
=
.html
)
...
...
@@ -25,6 +25,7 @@ DIST_SUBDIRS = design-paper spec
$(html_in)
:
$(
top_srcdir
)
/doc/asciidoc-helper.sh html @ASCIIDOC@ @SED@
$@
torify.html.in
:
torify.1.txt
tor-gencert.html.in
:
tor-gencert.1.txt
# Generate the manpage from asciidoc, but don't do
...
...
@@ -32,6 +33,7 @@ tor-gencert.html.in : tor-gencert.1.txt
$(man_in)
:
$(
top_srcdir
)
/doc/asciidoc-helper.sh man @A2X@ @SED@
$@
torify.1.in
:
torify.1.txt
tor-gencert.1.in
:
tor-gencert.1.txt
# use ../config.status to swap all machine-specific magic strings
...
...
@@ -39,5 +41,7 @@ tor-gencert.1.in : tor-gencert.1.txt
$(asciidoc_product)
:
../config.status
--file
=
$@
;
torify.1
:
torify.1.in
tor-gencert.1
:
tor-gencert.1.in
torify.html
:
torify.html.in
tor-gencert.html
:
tor-gencert.html.in
This diff is collapsed.
Click to expand it.
doc/torify.1
deleted
100644 → 0
+
0
−
42
View file @
2fc0c303
.TH torify 1 "" Jan-2009 ""
.\" manual page by Peter Palfrader and Jacob Appelbaum
.SH NAME
.LP
torify \- wrapper for torsocks or tsocks and tor
.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
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
that you would like to run socksified.
Please note that since both method use LD_PRELOAD, torify cannot be applied
to suid binaries.
.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
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.
.SH SEE ALSO
.BR tor (1),
.BR tor-resolve (1),
.BR torsocks (1),
.BR tsocks (1),
.BR tsocks.conf (5).
This diff is collapsed.
Click to expand it.
doc/torify.1.txt
0 → 100644
+
50
−
0
View file @
59a9908f
// 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
torify(1)
=========
Peter Palfrader
Jacob Appelbaum
NAME
----
torify - wrapper for torsocks or tsocks and tor
SYNOPSIS
--------
**torify** __application__ [__application's__ __arguments__]
DESCRIPTION
-----------
**torify** 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
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 that
you would like to run socksified. +
Please note that since both method use LD_PRELOAD, torify cannot be applied to
suid binaries.
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 normal system
resolver to your usual resolving nameservers. The **tor-resolve**(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.
SEE ALSO
--------
**tor**(1), **tor-resolve**(1), **torsocks**(1), **tsocks**(1),
**tsocks.conf**(5).
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment