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
I noticed that libsodium's memory managment encurages using allocators too, although they also offer the mlock, munlock, and memzero seperately too. Is an allocator used here only because constructors are just by convention in Rust?
Are there sitautions in which it suffices to simply call memzero via a newtype_drop macro, as used in sodiumoxide? Are there reasons private key material should not be kept on the stack? Is it for example bad to call madvice or mlock on the stack?
Apologies for the dumb qustions. ;)
The text was updated successfully, but these errors were encountered:
I noticed that libsodium's memory managment encurages using allocators too, although they also offer the
mlock
,munlock
, andmemzero
seperately too. Is an allocator used here only because constructors are just by convention in Rust?Are there sitautions in which it suffices to simply call memzero via a
newtype_drop
macro, as used in sodiumoxide? Are there reasons private key material should not be kept on the stack? Is it for example bad to callmadvice
ormlock
on the stack?Apologies for the dumb qustions. ;)
The text was updated successfully, but these errors were encountered: