On Thu 2016-12-08 22:01:44 -0500, Jeffrey Stedfast wrote:
I'll try to make a release this weekend. Working on getting a usable Linux system right now (I've been building on Mac but I can't make a release from that).
Great to hear, thank you! If you need a usable Linux system and you're willing to work on somoene else's hardware, i can probably set up a virtual machine for you to use, just let me know your requirements.
I think for now we should keep it on GMimeGpgContext since that's the only ctx that it affects. Did you discover that the S/MIME context could not support this? If it can, we could probably move it to the base class.
From first-principles, based on the underlying data: yes it can. In CMS (the S/MIME encryption format) the session keys are known as "content-encryption keys". see: https://tools.ietf.org/html/rfc5652#section-6.3 https://tools.ietf.org/html/rfc5652#section-6.4 That said, the current GMime S/MIME implementation won't support it, because it relies on gpgme, which in turn relies on gpgsm, and gpgsm does not support session-key extraction yet. However, i'm hoping that it will support it in the future: https://bugs.gnupg.org/gnupg/issue2862 So anyway, i'm happy to leave the choice of API up to you. Thanks for working on an updated release! --dkg
Attachment:
signature.asc
Description: PGP signature