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
When we delete our keyshare because we are leaving the signer set, we want to be sure it no longer exists on disk, rather than just being removed as an entry in the key-value database. That is - it should be overwritten by zero bytes.
My hunch is that we can achieve this by overwriting the value with a vector of zero bytes of the same length. We could do this in our wrapper to sled's remove method in the entropy-kvdb crate:
When we delete our keyshare because we are leaving the signer set, we want to be sure it no longer exists on disk, rather than just being removed as an entry in the key-value database. That is - it should be overwritten by zero bytes.
My hunch is that we can achieve this by overwriting the value with a vector of zero bytes of the same length. We could do this in our wrapper to sled's
remove
method in theentropy-kvdb
crate:entropy-core/crates/kvdb/src/encrypted_sled/kv.rs
Line 191 in 3e87482
But without knowing how sled represents values internally, we cannot be sure that this will reliably overwrite the original value.
I have made an issue in the sled repo asking this question, and if we don't hear back i would write a test and / or read the code to investigate.
The text was updated successfully, but these errors were encountered: