Changes between Version 11 and Version 12 of faq/admin/keyringer

Apr 20, 2012, 11:10:13 AM (9 years ago)
Nat Meysenburg



  • faq/admin/keyringer

    v11 v12  
    77To help us securely read and create new keys, we use a program called [;a=summary keyringer].
     9= Setting up Keyringer =
    910Members of the support team can access the keys by following these steps:
    4344pass assata
     47= Editing a Keyringer Entry =
     48From time to time you may need to edit a row in the keyring, for example after changing a password.
     50Assuming that you have keyringer set up properly, there is a  command should unlock the keys, and pass it to an editor. It also creates a decrypted temp file in the keyringer temp directory. The command is:
     53keyringer mfpl edit mfpl.asc
     56You will be prompted for your key auth (if it isn't already loaded). It will then check all signatures against the recipients file ({{{/path/to/keys/config/recipients/default}}}. Then it will present you with an option like:
     58Press any key to open the decrypted data in /usr/bin/emacsclient -a '' -t, Ctrl-C to abort
     61Pressing "any key" has never worked for me. However I can edit the tmp file. The tmp directory is in the mfpl keyring directory, ie {{{/path/to/keys/tmp}}}. After editing the tmp file, you can hit Ctrl-C in your terminal. This will encrypt the tmp file to all recipients in th recipients list, and overwrite the original.
     63Next you will need to commit your changes. Assuming your're in your {{{/path/to/keys/}}} dir, a simple:
     66git commit -a
     69should do the trick.
     71You will then need to push your changes so that the rest of the support team has access to the new password:
     74git push origin master