You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems impossible from the public API to overwrite the memory occupied by a BigUint. This is a dealbreaker for cryptographic applications since a BigUint may contain private keys for RSA or DH schemes.
Exposing the trait crate::biguint::IntDigits to the public API would solve that problem.
The text was updated successfully, but these errors were encountered:
It doesn't address realloc at all, which means old values may still be left on the heap.
Exposing the trait crate::biguint::IntDigits to the public API would solve that problem.
That requires exposing the digit size, which I explicitly don't want.
But if you're OK with a manual secure-delete like that, we could add a feature to impl Zeroize for BigUint and you could call that yourself, or you could create a Secret<BigUint> to zero on drop.
It seems impossible from the public API to overwrite the memory occupied by a
BigUint
. This is a dealbreaker for cryptographic applications since a BigUint may contain private keys for RSA or DH schemes.Exposing the trait
crate::biguint::IntDigits
to the public API would solve that problem.The text was updated successfully, but these errors were encountered: