authority-policy.txt 1.4 KB

1234567891011121314151617181920212223242526272829303132333435363738
  1. Here's a first set of guidelines for how to pick new directory
  2. authorities.
  3. (These won't be formal criteria -- we need to keep this loose since
  4. we're making it up as we go.)
  5. o Stability:
  6. - Must be a low-downtime Tor server (computer as well as network).
  7. - Must have a static IP.
  8. - The operator must have been running a stable Tor server for at least
  9. 3 months.
  10. - Must intend for this server to stick around for the next 12 months
  11. or more.
  12. - Must not hibernate.
  13. - Should not be an exit node (as this increases the risk both of
  14. downtime and of key compromise).
  15. o Performance:
  16. - Must have sufficient bandwidth: at least 300 kB/s symmetric,
  17. though in practice the inbound traffic can be considerably less.
  18. o Availability:
  19. - Must be available to upgrade within a few days in most cases.
  20. (While we're still developing Tor, we periodically find bugs that
  21. impact the whole network and require dirserver upgrades.)
  22. o Integrity:
  23. - Must promise not to censor or attack the network and users.
  24. - Should be run by somebody that Tor (i.e. Roger) knows.
  25. - Should be widely regarded as fair/trustworthy, or at least
  26. known, by many people.
  27. - If somebody asks you to backdoor or change your server, legally or
  28. otherwise, you will fight it to the extent of your abilities. If
  29. you fail to fight it, you must shut down the Tor server and notify
  30. us that you have.
  31. - Dirservers (and operators) in a variety of jurisdictions are best.