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

Making zeroization optional #315

Open
brycx opened this issue Jan 9, 2023 · 0 comments
Open

Making zeroization optional #315

brycx opened this issue Jan 9, 2023 · 0 comments

Comments

@brycx
Copy link
Member

brycx commented Jan 9, 2023

As the discussion in #59 also points out, zeroizing values allocated on the stack doesn't really give us any guarantees that copies aren't left around. Right now, zeroization is enabled by default and so even if users don't consider this a part of their threat-model, they still pay the performance penalty.

Perhaps it's more sensible to make zeroization of data optional, still keeping it on by default but allowing opt-out if users specifically don't care about this.

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

No branches or pull requests

1 participant