commit a030102c3181bd4276ac0e9ca829521379195768 Author: juga0 juga@riseup.net Date: Wed Jan 23 16:40:14 2019 +0000
docs: remove section that is already in DEPLOY --- docs/source/specification.rst | 8 -------- 1 file changed, 8 deletions(-)
diff --git a/docs/source/specification.rst b/docs/source/specification.rst index 598465f..ee99f3d 100644 --- a/docs/source/specification.rst +++ b/docs/source/specification.rst @@ -52,14 +52,6 @@ This document describes the implementation contained within the accompanying Anatomy of a Tor network using sbws -----------------------------------
-First and foremost, there needs to be one or more webservers that exist -somewhere on the Internet. They MUST serve up a file of at least some minimum -size, and MUST support both HTTP GET and HEAD requests on that file. For both -HTTP verbs, they MUST support requests with the Range header and MUST support -*not* compressing responses. Beyond these requirements, the webservers MAY support -TLS connections, optionally with a valid certificate. Both apache and nginx fit -these requirements. - Every directory authority that wishes to also vote on relay bandwidth (AKA a bandwidth authority) MUST run one or more sbws scanner clients (or trust someone to run one or more sbws scanner clients for them). The scanners run