[issue137] composer chooses to encrypt/sign with OpenPGP,
although no encrypt-to-self keys are configured for OpenPGP
aegypten-issues at intevation.de
Wed Apr 7 12:33:48 CEST 2004
New submission from Marc Mutz <marc at klaralvdalens-datakonsult.se>:
Create an entry with the following preferences:
Allowed protocols: OpenPGP/MIME, S/MIME, S/MIME opaque
Sign: Always sign
Encrypt: Ask Whenever Possible
Assign both preferred OpenPGP and S/MIME keys to that contact.
Open a composer, choose an identity with no OpenPGP sign/encrypt keys, but only
S/MIME sign/encrypt keys.
Uncheck the sign and the encrypt buttons and choose "Any" in the format
On send, you'll get an error message telling you that it chose to encrypt/sign
with OpenPGP, but that there is no OpenPGP encrypt-to-self key available. If
you have disabled encrypt-to-self, then it will ask the same thing b/c of the
missing sign key.
It should use S/MIME instead, of course.
title: composer chooses to encrypt/sign with OpenPGP, although no encrypt-to-self keys are configured for OpenPGP
Aegypten issue tracker <aegypten-issues at intevation.de>
More information about the Gpa-dev