[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #30627 [Internal Services/Tor Sysadmin Team]: document how to map a service back to an underlying host
#30627: document how to map a service back to an underlying host
-------------------------------------------------+-------------------------
Reporter: arma | Owner: tpa
Type: enhancement | Status:
| reopened
Priority: Medium | Milestone:
Component: Internal Services/Tor Sysadmin Team | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Changes (by arma):
* status: closed => reopened
* resolution: fixed =>
Comment:
Thanks!
I've looked at the doc (and fixed a typo), but now the big question is
that it shifts from which 'you' it thinks it's addressing:
* At the beginning it is about how you can figure out which service or
server is involved when something isn't working
* And then suddenly it's about how you need to file a ticket with Hetzner.
Anybody who notices a service is down can be the first you. But most of
them shouldn't be the ones to file a ticket with Hetzner, right? Most of
them should... mail torproject-admin? Find us on irc?
Speaking of which, when I want to approach hetzner, I go to the tor-
passwords repo and "gpg < hosts-extra-info" and now I am more informed.
But I notice that file isn't encrypted to anarcat. I guess that we have
moved to some other approach. But I wonder what it is. :)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30627#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs