[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:
-------------------------------------------------+-------------------------

Comment (by anarcat):

 >  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?

 Well, this guide is directed mostly at sysadmins. Most people should
 "contact us", which is:

 https://help.torproject.org/tsa/doc/how-to-get-help/

 Maybe I should just throw that up there?

 >  Speaking of which, when I want to approach hetzner, I go to the tor-
 passwords repo and "gpg < hosts-extra-info"

 By the way, you '''really''' don't want to `gpg < foo`. It lets gpg "guess
 what you want", and it can do some pretty nasty stuff, in theory. In
 practice, it might be safe, but I was really unhappy about what I saw
 auditing that source path and I '''strongly recommend''' heeding the
 warnings that now bug you in GPG 2. What you want is `gpg -d < foo` or
 `gpg --decrypt < foo`.

 > 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. :)

 Wait what? It isn't encrypt to me? What do you mean? I just git pulled the
 file and I *can* decrypt it.

 We haven't changed approach on that front, as far as I know.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30627#comment:5>
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