Shawn Nock <nock@xxxxxxxxx> writes: > Hello friends, > > As I recall, there are several exits running on DigitalOcean's > infrastructure. This is presented FYI: > > Background: I've run an exit on DigitalOcean for about a year without > issues (lost track of uptime duing heartbleed key regen). It wasn't > hidden (the droplet name was 'tor-exit') and it had valid reverse DNS > and the standard informational page was hosted there. At the time of > droplet creation, tor exits were not prohibited by their ToS. I've > mentioned to DigitalOcean staff during support tickets that it was a > Tor exit. Update: HOLY CRAP! > Hello > > Thanks for your well worded response. > > You have argued your case well and we have decided to allow your tor > exit node. > > However please understand this is a unique case with a custom > solution, by no means does this reflect our overall policy on TOR. > > All cases are reviewed individually. > > We will let you know if we see any further issues. > > Thanks for your understanding, we have resumed your tor node. > > Let us know if you have any other questions or feedback > > Regards > Support -- Shawn Nock (OpenPGP: 0x6FDA11EE 3BC412E3)
Attachment:
pgpJucy8TOPqG.pgp
Description: PGP signature
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays