Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2024-12-28 16:59:40 -05:00
Code Issues Packages Projects Releases Wiki Activity

Update split-gpg.md

Browse Source
This commit is contained in:
Daniel Gonzalez Gasull 2018-11-09 18:35:56 +08:00 committed by GitHub
parent 1ea35ffe16
commit 0512a3807c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
security/split-gpg.md
View File

@ -79,7 +79,7 @@ The Split GPG client will fail to sign or encrypt if the private key in the
GnuPG backend is protected by a passphrase, it will give a *"Inappropriate ioctl GnuPG backend is protected by a passphrase, it will give a *"Inappropriate ioctl
for device"* error. Avoid setting passphrases for the private keys in the GPG for device"* error. Avoid setting passphrases for the private keys in the GPG
backend domain, it won't provide extra security anyway, as explained before. backend domain, it won't provide extra security anyway, as explained before.
Unfortunately you can set empty passphrases no matter what `pinentry-*` package Unfortunately you can't set empty passphrases no matter what `pinentry-*` package
you are using. If you are generating a new key pair, or if you have a private you are using. If you are generating a new key pair, or if you have a private
key that already has a passphrase and use key that already has a passphrase and use
`gpg2 --edit-key {key_id}`, then `passwd`, then pinentry won't allow setting an `gpg2 --edit-key {key_id}`, then `passwd`, then pinentry won't allow setting an