Improve user doc for backup/restore operations

This commit is contained in:
thomsh 2020-01-03 11:46:01 +13:00
parent f7fff68d32
commit 764521006b
No known key found for this signature in database
GPG Key ID: A0EA57E4A81D26AB

View File

@ -1136,6 +1136,8 @@ In a general manner it is better to also save your keys with ``--backup-keys`` o
Note that backup and restore works on current slot, so you have to perform a backup per slot
even if some data are shared. You can precise the slot/backup to restore with ``--slot``
If you encounter an error when performing the backup/restore, reload your scdaemon with
``gpgconf --reload scdaemon``
Backup and Restore example
@ -1154,12 +1156,13 @@ backup command without private keys:
full restore command:
| ``python3 -m gpgcard.gpgcli --backup --pinpad --file my_bck_file_name.pickle``
| ``python3 -m gpgcard.gpgcli --restore --pinpad --file my_bck_file_name.pickle``
full restore command with seed key generation:
| ``python3 -m gpgcard.gpgcli --backup --pinpad --seed --file my_bck_file_name.pickle``
| ``python3 -m gpgcard.gpgcli --restore --pinpad --seed-key --file my_bck_file_name.pickle``
Restore without backup
~~~~~~~~~~~~~~~~~~~~~~