Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PGPMessage.decrypt and PGPKey.decrypt should offer the ability to return a session key to the caller #390

Open
dkg opened this issue Feb 2, 2022 · 0 comments

Comments

@dkg
Copy link
Contributor

dkg commented Feb 2, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant