-
-
Notifications
You must be signed in to change notification settings - Fork 369
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
Cache Sealing and Opening keys in secrets #17
Comments
@stammw is this something you want to try next? (The description isn't quite valid anymore as some of the type names are different from when I wrote this up, but the gist of it still holds.) |
Sure ! I'll see what I can come up with ! |
Cool. Don't hesitate to ask if you have questions! |
@djc I believe this issue can be closed. |
Yup! Thanks for working on it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
crypto
module currently has aPacketKey
type that reconstructs the relevantSealingKey
andOpeningKey
for everyseal
oropen
operation. There should be a smarter way to structure the types in thecrypto
module so that aSecret
has direct access to long-livedKey
instances.The text was updated successfully, but these errors were encountered: