1
0
Fork 0
mirror of synced 2024-04-26 00:22:17 +12:00

Add a note that cp on sockets will fail, but is ok

Per issue #25.

Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
This commit is contained in:
Konstantin Ryabitsev 2017-12-18 08:32:17 -05:00
parent 8a9d547d3e
commit 126e4f0b5d
No known key found for this signature in database
GPG key ID: 34BAB80AF9F247B8

View file

@ -578,7 +578,10 @@ Once you know the full mount path, copy your entire GnuPG directory there:
$ cp -rp ~/.gnupg [/media/disk/name]/gnupg-backup $ cp -rp ~/.gnupg [/media/disk/name]/gnupg-backup
You should now test to make sure it still works: (Note: If you get any `Operation not supported on socket` errors, those are
benign and you can ignore them.)
You should now test to make sure everything still works:
$ gpg --homedir=[/media/disk/name]/gnupg-backup --list-key [fpr] $ gpg --homedir=[/media/disk/name]/gnupg-backup --list-key [fpr]
@ -591,8 +594,8 @@ adding or revoking subkeys, or signing other people's keys.
#### Remove the master key #### Remove the master key
Please see the previous section and make sure you have backed up your GnuPG Please see the previous section and make sure you have backed up your GnuPG
directory in its entirety. What we are about to do will make your key useless directory in its entirety. What we are about to do will render your key
if you do not have a usable backup! useless if you do not have a usable backup!
First, identify the keygrip of your master key: First, identify the keygrip of your master key: