#33134: Improve documentation for interacting with db.torproject.org
-----------------------------------------------------+-----------------
     Reporter:  gk                                   |      Owner:  tpa
         Type:  enhancement                          |     Status:  new
     Priority:  Medium                               |  Milestone:
    Component:  Internal Services/Tor Sysadmin Team  |    Version:
     Severity:  Normal                               |   Keywords:
Actual Points:                                       |  Parent ID:
       Points:                                       |   Reviewer:
      Sponsor:                                       |
-----------------------------------------------------+-----------------
 I've been trying to set up a sudo password for a particular host, and
 while consulting the help on https://help.torproject.org/tsa/howto/ldap/ I
 figured we could think about improving it. In particular:

 1) When looking at the documentation about how to use
 [email protected] it says for SSH keys to use `gpg --armor
 --clear` while the troubleshooting of changes failures warns that clear
 signing is often causing issues in the SSH key context. So, maybe just use
 `gpg --armor --sign` in the SSH keys change documentation as well? (As
 done in the one for changing the password in the previous paragraph)

 2) It seems at least some clients have "PGP/MIME" chosen by default but
 [email protected] is choking on that. Maybe make clear that
 "Inline PGP" needs to get used? That could be done in an additional
 sentence before talking about the SSH keys and "show".

 3) s/If the single word show appears on a line then/If the single word
 show appears on a line in a PGP signed mail then/

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33134>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Reply via email to