george/blackbox
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Improve info about expired GPG keys.

Browse Source
This commit is contained in:
Tom Limoncelli
2017-06-16 12:04:08 -04:00
parent e1f03e4a74
commit bdd983b96d
1 changed files with 14 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
README.md
View File

@@ -600,18 +600,27 @@ rm -rf /tmp/NEWMASTER
Also shred any other temporary files you may have made. Also shred any other temporary files you may have made.
Replace expired keys Replacing expired keys
==================== ======================
If any one admin's key expires, you can no longer encrypt files. You will need to replace the key and re-encrypt. If someone's key has already expired, blackbox will stop
encrypting. You see this error:
- Step 0: You see this error:
``` ```
$ blackbox_edit_end modified_file.txt $ blackbox_edit_end modified_file.txt
--> Error: can't re-encrypt because a key has expired. --> Error: can't re-encrypt because a key has expired.
``` ```
You can also detect keys that are about to expire by issuing this command and manually reviewing the "expired:" dates:
gpg --homedir=keyrings/live --list-keys
or... list UIDs that will expire within 1 month from today: (Warning: this also lists keys without an expiration date)
gpg --homedir=keyrings/live --list-keys --with-colons --fixed-list-mode | grep ^uid | awk -F: '$6 < '$(( $(date +%s) + 2592000))
Here's how to replace the key:
- Step 1. Administrator removes expired user: - Step 1. Administrator removes expired user:
Warning: This process will erase any unencrypted files that you were in the process of editing. Copy them elsewhere and restore the changes when done. Warning: This process will erase any unencrypted files that you were in the process of editing. Copy them elsewhere and restore the changes when done.