

6·
3 days agoI’m sure you could mount an encrypted volume.
Or just have the keepas db on a usb stick or something
I’m sure you could mount an encrypted volume.
Or just have the keepas db on a usb stick or something
I feel like “look at twitter” is probably enough of a defence to decline president musk.
It would probably need to be wordier for court proceedings.
My experience of checksums are in things like serial where they can potentially recover a corrupt bit.
I presume in the case of encryption, a checksum is more of a hash of the raw data? Like a one-way deterministic compute. Easy to get a hash of data, extremely difficult to get data from a hash.
In which case, it’s fine. Passwords are hashed (granted, multiple times), but a cryptographically secure hash is not to be underestimated.
When you solve the issue, take a pause and then walk back the problem and how to fix it.
If it’s a “forgot where something was”, take a pause then start with “sorry bout that, it’s this…”.
Own the mistake, learn from it, let others learn from it. But dont waste everyone’s time