| 46 | |
| 47 | = Editing a Keyringer Entry = |
| 48 | From time to time you may need to edit a row in the keyring, for example after changing a password. |
| 49 | |
| 50 | Assuming 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: |
| 51 | |
| 52 | {{{ |
| 53 | keyringer mfpl edit mfpl.asc |
| 54 | }}} |
| 55 | |
| 56 | You 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: |
| 57 | {{{ |
| 58 | Press any key to open the decrypted data in /usr/bin/emacsclient -a '' -t, Ctrl-C to abort |
| 59 | }}} |
| 60 | |
| 61 | Pressing "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. |
| 62 | |
| 63 | Next you will need to commit your changes. Assuming your're in your {{{/path/to/keys/}}} dir, a simple: |
| 64 | |
| 65 | {{{ |
| 66 | git commit -a |
| 67 | }}} |
| 68 | |
| 69 | should do the trick. |
| 70 | |
| 71 | You will then need to push your changes so that the rest of the support team has access to the new password: |
| 72 | |
| 73 | {{{ |
| 74 | git push origin master |
| 75 | }}} |