New submission from Marc Mutz <marc@klaralvdalens-datakonsult.se>:
Try this in current KMail (aegypten_2_0_0_pre3_release tag):
Define an identity with only S/MIME keys (see #132 for why).
Open a composer, select the above identity, select "S/MIME" format,
say yes to sign? and no to encrypt? and. This will succeed.
Do the same, but use "S/MIME opaque". This will fail with an invalid crypto
engine error.
Why is the a backend problem?
Run KMail in gdb, and set a break point to gpgme_op_sign.
In the first, case above (the one orginally succeeding), change the mode
parameter inside a gpgme funtion from the normal GPGME_SIG_MODE_DETACH to
GPGME_SIG_MODE_NORMAL. -> Signing fails, and we have only changed this single
variable.
Likewise, in the originally failing case of S/MIME opaque, set the mode
parameter from the normal GPGME_SIG_MODE_NORMAL to GPGME_SIG_MODE_DETACH.
-> Signing will succeed, although it will of course not result in a valid
message, due to the opaque/detached mismatch between gpgme and kmail.
----------
assignedto: werner
messages: 613
nosy: marc, werner
priority: critical
status: unread
title: gpgme/gpgsm: GPGME_SIG_MODE_NORMAL doesn't work (at least for cms)
topic: GPGME, gpgsm
______________________________________________________
Aegypten issue tracker <aegypten-issues@intevation.de>
<https://intevation.de/roundup/aegypten/issue134>
______________________________________________________
Try this in current KMail (aegypten_2_0_0_pre3_release tag):
Define an identity with only S/MIME keys (see #132 for why).
Open a composer, select the above identity, select "S/MIME" format,
say yes to sign? and no to encrypt? and. This will succeed.
Do the same, but use "S/MIME opaque". This will fail with an invalid crypto
engine error.
Why is the a backend problem?
Run KMail in gdb, and set a break point to gpgme_op_sign.
In the first, case above (the one orginally succeeding), change the mode
parameter inside a gpgme funtion from the normal GPGME_SIG_MODE_DETACH to
GPGME_SIG_MODE_NORMAL. -> Signing fails, and we have only changed this single
variable.
Likewise, in the originally failing case of S/MIME opaque, set the mode
parameter from the normal GPGME_SIG_MODE_NORMAL to GPGME_SIG_MODE_DETACH.
-> Signing will succeed, although it will of course not result in a valid
message, due to the opaque/detached mismatch between gpgme and kmail.
----------
assignedto: werner
messages: 613
nosy: marc, werner
priority: critical
status: unread
title: gpgme/gpgsm: GPGME_SIG_MODE_NORMAL doesn't work (at least for cms)
topic: GPGME, gpgsm
______________________________________________________
Aegypten issue tracker <aegypten-issues@intevation.de>
<https://intevation.de/roundup/aegypten/issue134>
______________________________________________________