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

use direct ByteBuffer instead of byte[] in cryptographic operations #2

Open
andy-goryachev opened this issue Jun 23, 2019 · 0 comments

Comments

@andy-goryachev
Copy link
Owner

andy-goryachev commented Jun 23, 2019

Generational garbage collector may leave copies of sensitive data in multiple locations in RAM. We should use direct ByteBuffer for any crypto operations instead of byte[].

See
https://news.ycombinator.com/item?id=20241363

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

No branches or pull requests

1 participant