Re: [Enigmail] Question for the passphrase of a key which is not involved in encrypting an email

"Robert J. Hansen" <[email protected]> Wed, 6 May 2020 11:36:46 -0400
Newsgroups gmane.comp.mozilla.enigmail.general
Message-ID <[email protected]>
> In order to help him, I created a new public+private key with Enigmail.
> Although using a key without a passphrase is not recommended, I
> generated one without it. Then I sent an encrypted test email to himself
> using the newly generated public key.

A key without a passphrase is completely acceptable, depending on your
particular security needs.  Please don't believe you're doing it wrong.
 So long as you do it after considering exactly what your needs are,
we're happy.  :)

> Even after I had _disabled_ the old key under Enigmail's key management
> (and a later reboot of course), Thunderbird/Enigmail still asks for the
> passphrase of the old key before decrypting a mail encrypted with the
> new key (the one without a passphrase)!

The most obvious culprit is the ~/.gnupg/gpg.conf file.  Somewhere in
there is a configuration option that's adding the newly-revoked/disabled
key to your recipients list (look for "encrypt-to", mostly).  When you
created this new test email, GnuPG silently added the old key to the
list of recipients in accordance with the configuration file telling it
to do so.

Now, whenever you try to decrypt that message GnuPG sees it was
encrypted to the old key and it asks you for the passphrase.  Once you
cancel out of that, it sees it was also encrypted to the new key and
uses that one, which has no passphrase.

_______________________________________________
enigmail-users mailing list
[email protected]
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
signature.asc (application/pgp-signature, 821 B)
-----BEGIN PGP SIGNATURE-----

iQGzBAEBCgAdFiEEzBG+fLvtd7Eg83sBHcvcAbREJ8cFAl6y2ZQACgkQHcvcAbRE
J8fzjwv/a0aT4ktqKK4D/ZQbYzFUcxeZOXhOiom73uIBWjF4EagjqQBISh0nB1fW
3rrw4BBULovB6d11m0juuDQ2tVYZaVdBPOQrU5cu3wpoJpjX8CbAgVPdWVt1Qe9d
f8KH1wo+SWPDUp4R+IJy+gjw38KXL7VaeYD8Ngkh6dPXriZOPqpL/pJHHsEjg8fL
p6aMlI1MPGOI2a79WjQStTNPMCUdkHNXnHFcIcQuor6S7jeaVYrxWn4hxxVQEIer
jEEUL0TiAkQJi5mZ/O2qdDEeXIJNgZoP0LOcs4WB+sFaUC9nMdCozdskCG7gwaj+
jpbeF9frAG6Q261EaK5lVvoQlhWZeCqDU3w9c61dBITpr2FVaxlcab91Nq253+JV
2SyIQLW5KcjpmDROrV6B7ihX7Hs0ea438O3Wrvcjc1YIWRJ9ShiJhB/ykxCl/5ab
aH4X5eI/9unemxuTc1ggVj2nsvKcCslhhUFHNCUF+KGm4kfzONrejAR+gNwPXcPN
koKz1G9KiHUEARYKAB0WIQRL8gQq4o9iuBc26MuoPK6U09w4cwUCXrLZlQAKCRCo
PK6U09w4c8NbAQCsE0vuz9TlKUtoL1RqHCs/ZFPYSuuH3tIpu7Rey29tZwD+J9F6
npl160Rc3lwA5F/CwkoyedRt9+o88ZyKvezwkwE=
=rjsO
-----END PGP SIGNATURE-----