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

Secret values not erased #12

Closed
moCello opened this issue Apr 17, 2024 · 0 comments · Fixed by #15
Closed

Secret values not erased #12

moCello opened this issue Apr 17, 2024 · 0 comments · Fixed by #15
Assignees
Labels
fix:bug Something isn't working type:enhancement Issues concerning code or feature improvement (performance, refactoring, etc)
Milestone

Comments

@moCello
Copy link
Member

moCello commented Apr 17, 2024

Summary

Add a way to securely erase sensitive data from memory when types go out of scope.

Possible solution design or implementation

Add Zeroize trait, remove Copy trait on all structs carrying sensitive data.

Additional context

See bls12_381-bls #5

@HDauven HDauven added this to the Mainnet milestone Apr 17, 2024
@HDauven HDauven added fix:bug Something isn't working type:enhancement Issues concerning code or feature improvement (performance, refactoring, etc) labels Apr 17, 2024
moCello added a commit that referenced this issue Apr 23, 2024
moCello added a commit that referenced this issue Apr 23, 2024
moCello added a commit that referenced this issue Apr 23, 2024
moCello added a commit that referenced this issue Apr 24, 2024
moCello added a commit that referenced this issue Apr 24, 2024
@moCello moCello mentioned this issue Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix:bug Something isn't working type:enhancement Issues concerning code or feature improvement (performance, refactoring, etc)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants