On 30.04.18 14:50, Jeff Burdges wrote: > > I’ve noticed some confusing behaviours: > > > First, there is a spurious 2048 bit RSA key being created, which lacks any > passphrase, when using Thunderbird 52.7.0 with Enigmail 2.0.2. There is > already a key for the email account in question, although the email address > is not set to be the primary uid, and the key has a passphrase, although > gpg-agent works fine for other MUAs. > > There are numerous problems with creating a new key when a valid key already > exists: It breaks for users who decrypt their mail on multiple devices. > It’s insecure for users who manage their key’s more rigorously, like by > keeping their root SC private key offline, using short expirations, using a > smart card, etc. > > > Second, there is no way to suppress this behaviour from within Thunderbird. > If you go to [account] -> View settings for this account -> OpenGPG Security > and then click the Enable OpenPGP security Enigmail toggle box then may > select to use a specific key, but this setting appears to be ignored and > sometimes gets erased later. > > As an aside, anytime you click this box it asks if you want to disable pEp, > but clicking cancel still checks the box, so you must uncheck it and click > cancel again. > > > At present the only easy solution I’ve found is: > > gpg -K | grep rsa2048 # yields the spurious_key_id assuming you never use > 2048 bit keys yourself > gpg --delete-secret-keys spurious_key_id > sudo chown root .gnupg/private-keys-v1.d > sudo chmod 550 .gnupg/private-keys-v1.d > > I’ve only done cursory testing of this workaround, but no obvious harmful > side effects arose. You must obviously reverse these changes to do private > key management, preferably without Thunderbird running. Also contacts might > send a messages encrypted to the wrong key, so they may need to run: > > gpg --delete-keys spurious_key_id > > You could easily wind up with numerous spurious_key_id by messing around with > this. Assuming you’ve never used a 2048 bit key then your contacts could > generate commands to delete them all by running: > > gpg -k | grep your_email_address -B 2 | grep rsa2048 | cut -c15-33 | sed -e > 's/^/gpg --delete-keys /' > > > A cleaner workaround would be replacing the gpg binary used by Enigmail/pEp > with a wrapper script that blocks attempts to create new keys, perhaps by > blocking the --quick-generate-key option, or else permits Enigmail/pEp to > generate its own key but adds the —homedir to prevent breaking the user’s > .gnupg database. > > I’m hoping that someone here can tell me how to force Enigmail/pEp in > Thunderbird to use the correct GPG key, preferably without deactivating pEp.
To explain a little more what's going on: at startup, the pEp adapter tries to figure out if there is a key for each account. If not, it creates a key (without a password - pEp does not use passwords to protect the keys). There seems to be a bug in that logic which leads to pEp creating a new key whenever it starts up because it does not recognize your existing key. AFAICT there is no workaround for this, unless you switch to the "regular" Enigmail mode until that's solved. -Patrick
signature.asc
Description: OpenPGP digital signature
_______________________________________________ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
