From 0512a3807c5de01b5a938d0892efd4afe3279960 Mon Sep 17 00:00:00 2001 From: Daniel Gonzalez Gasull Date: Fri, 9 Nov 2018 18:35:56 +0800 Subject: [PATCH] Update split-gpg.md --- security/split-gpg.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/security/split-gpg.md b/security/split-gpg.md index 5497551b..64543730 100644 --- a/security/split-gpg.md +++ b/security/split-gpg.md @@ -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 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. -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 key that already has a passphrase and use `gpg2 --edit-key {key_id}`, then `passwd`, then pinentry won't allow setting an