You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is the converse operation of #389 -- when decrypting, it can be useful to extract a session key from the decryption, to store it for later reuse.
This avoids asymmetric operations (when using PKESK), and S2K operations (when using SKESK) in the future, and also permits tricks like destruction of decryption-capable keys without losing the message itself, or other MUA optimizations (see for example index.decrypt from notmuch-config).
To make this possible, it would be nice if the two high-level decryption operations (PGPMessage.decrypt for passphrase-based decryption, and PGPKey.decrypt for secret-key-based decryption) could somehow return a session key to the user.
The text was updated successfully, but these errors were encountered:
This is the converse operation of #389 -- when decrypting, it can be useful to extract a session key from the decryption, to store it for later reuse.
This avoids asymmetric operations (when using PKESK), and S2K operations (when using SKESK) in the future, and also permits tricks like destruction of decryption-capable keys without losing the message itself, or other MUA optimizations (see for example
index.decrypt
from notmuch-config).To make this possible, it would be nice if the two high-level decryption operations (
PGPMessage.decrypt
for passphrase-based decryption, andPGPKey.decrypt
for secret-key-based decryption) could somehow return a session key to the user.The text was updated successfully, but these errors were encountered: