Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
T
Tor
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
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
Benjamin J. Thompson
Tor
Commits
2fa01764
Commit
2fa01764
authored
20 years ago
by
Roger Dingledine
Browse files
Options
Downloads
Patches
Plain Diff
stop trying to maintain two separate doc sections
now README points to tor-doc.html svn:r2632
parent
790349c6
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README
+3
-29
3 additions, 29 deletions
README
with
3 additions
and
29 deletions
README
+
3
−
29
View file @
2fa01764
...
...
@@ -17,38 +17,11 @@ doesn't work for you.
Do you want to run a tor server?
We're looking for people with reasonably reliable Internet connections,
that have at least 1Mbit each way. Currently we don't use all of that,
but we want it available for burst traffic.
(The Tor server doesn't need to be run as root, and doesn't need any
special system permissions or kernel mods. You should probably run it
as its own user though, especially if you run an identd service too.)
First, copy torrc.sample to torrc (by default it's in
/usr/local/etc/tor/), and edit the middle part. Create the
DataDirectory, and make sure it's owned by the uid/gid that will be
running tor. Fix your system clock so it's not too far off. Make sure
name resolution works.
Then run tor to generate keys. One of the files generated
in your DataDirectory is your 'fingerprint' file. Mail it to
tor-ops@freehaven.net.
Please also tell us in that mail who you are, so we know whom to contact
if there's any problem. Also describe what kind of connectivity the new
server will have. If possible PGP sign your mail.
You may find the initscript in contrib/tor.sh useful if you
want to set up Tor to start at boot.
See http://freehaven.net/tor/doc/tor-doc.html#server
Do you want to run a hidden service?
Copy torrc.sample to torrc (by default it's in /usr/local/etc/tor/), and
edit the bottom part. Then run Tor. It will create each HiddenServiceDir
you have configured, and it will create a 'hostname' file which
specifies the url (xyz.onion) for that service. You can tell people
the url, and they can connect to it via their Tor client.
See http://freehaven.net/tor/doc/tor-doc.html#hidden-service
Configuring tsocks:
...
...
@@ -66,3 +39,4 @@ Configuring tsocks:
(On Windows, you may want to look at the Hummingbird SOCKS client,
or at SocksCap, instead.)
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