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
fc75bb3a
Commit
fc75bb3a
authored
17 years ago
by
Roger Dingledine
Browse files
Options
Downloads
Patches
Plain Diff
first cut of a policy for what new directory authorities we want.
svn:r11954
parent
738d178f
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
doc/contrib/authority-policy.txt
+34
-0
34 additions, 0 deletions
doc/contrib/authority-policy.txt
with
34 additions
and
0 deletions
doc/contrib/authority-policy.txt
0 → 100644
+
34
−
0
View file @
fc75bb3a
Here's a first set of guidelines for how to pick new directory
authorities.
(These won't be formal criteria -- we need to keep this loose since
we're making it up as we go.)
o Stability:
- Must be a low-downtime Tor server (computer as well as network).
- Must have a static IP.
- Must have been a stable Tor server for at least 3 months.
- Must intend to stick around for the next 12 months or more.
- Must not hibernate.
o Performance:
- Must have sufficient bandwidth: at least 300 kB/s symmetric,
though in practice the inbound traffic can be considerably less.
o Availability:
- Must be available to upgrade within a few days in most cases.
(While we're still developing Tor, we periodically find bugs that
impact the whole network and require dirserver upgrades.)
o Integrity:
- Must promise not to censor or attack the network and users.
- Should be run by somebody that Tor (i.e. Roger) knows.
- Should be widely regarded as fair/trustworthy, or at least
known, by many people.
- If somebody asks you to backdoor or change your server, legally or
otherwise, you will fight it to the extent of your abilities. If
you fail to fight it, you must shut down the Tor server and notify
us that you have.
- Dirservers (and operators) in a variety of jurisdictions are best.
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