mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2024-12-25 15:29:29 -05:00
Fixes #4901 'Outdated paragraph in Split GPG limitations section'
This commit is contained in:
parent
7772aa414b
commit
c3b338635a
@ -57,11 +57,8 @@ This way it would be easy to spot unexpected requests to decrypt documents.
|
|||||||
Doing so won't provide any extra security anyway, as explained [above][intro] and [below][using Split GPG with subkeys].
|
Doing so won't provide any extra security anyway, as explained [above][intro] and [below][using Split GPG with subkeys].
|
||||||
If you are generating a new key pair, or if you have a private key that already has a passphrase, you can use `gpg2 --edit-key <key_id>` then `passwd` to set an empty passphrase.
|
If you are generating a new key pair, or if you have a private key that already has a passphrase, you can use `gpg2 --edit-key <key_id>` then `passwd` to set an empty passphrase.
|
||||||
Note that `pinentry` might show an error when you try to set an empty passphrase, but it will still make the change.
|
Note that `pinentry` might show an error when you try to set an empty passphrase, but it will still make the change.
|
||||||
<<<<<<< HEAD
|
(See [this StackExchange answer][se-pinentry] for more information.)
|
||||||
(See [this StackExchange answer][se-pinentry] for more information.) Note: The error shows only if you **do not** have graphical pinentry installed.
|
Note: The error shows only if you **do not** have graphical pinentry installed.
|
||||||
=======
|
|
||||||
(See [this StackExchange answer][se-pinentry] for more information.) Note: The error shows only if you **do not** have graphical pinentry installed. The Split GPG client lets you use password-protected keys, and the vault qube will show the passphrase.
|
|
||||||
>>>>>>> c7309fe6150dee28787ffd8fc584fa3114d10179
|
|
||||||
|
|
||||||
## Configuring Split GPG ##
|
## Configuring Split GPG ##
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user