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

Does not lock scratch space in RAM #2

Open
alexwebr opened this issue Jul 2, 2013 · 0 comments
Open

Does not lock scratch space in RAM #2

alexwebr opened this issue Jul 2, 2013 · 0 comments
Assignees
Labels

Comments

@alexwebr
Copy link
Owner

alexwebr commented Jul 2, 2013

The s20_crypt function uses automatic variables to store sensitive material (including, at various points, the key and the derived keystream blocks) during a cryptographic operation.

s20_crypt does not lock the memory ranges containing these variables in memory (using mlock or similar), and because the variables are automatic, does not make it easy for the user of this library to do so.

This could allow sensitive material (keys and keystream blocks) to be swapped out to disk.

@ghost ghost assigned alexwebr Jul 2, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant