-
Notifications
You must be signed in to change notification settings - Fork 475
Clear encryption data when no longer needed #2616
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
Conversation
|
There are still some issues with this PR, just looking to get feedback on the approach. |
| kekId = null; | ||
| Arrays.fill(encFek, (byte) 0); | ||
| } | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These changes look good so far. I like using AutoCloseable, that is a good idea.
| } | ||
| } else { | ||
| // read crypto parameters and get decrypter | ||
| this.in.seek(offsetCryptoParameters); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We might want to put some checks in to ensure that the CryptoService is open so we don't write null values to the file.
ctubbsii
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no issue with that
IIRC most of the changes here have to do with the fact that CryptoService is now AutoClosable |
The changes in #2197 are also incomplete so that would be another reason to wait and could be why this PR looks so big. |
|
Closing this for now as I'm not sure that adding AutoCloseable to the CryptoService is the right thing to do. |
No description provided.