mirror of
https://github.com/sunknudsen/privacy-guides.git
synced 2025-02-23 09:13:56 +00:00
Moved footnote to heads-up
This commit is contained in:
parent
ec5c6f2963
commit
d8309ca9c9
@ -289,6 +289,8 @@ chmod +x /usr/local/bin/check.sh
|
||||
|
||||
### Backup
|
||||
|
||||
> Heads-up: store hash in safe place such as password manager (not on same device as backup).
|
||||
|
||||
```console
|
||||
$ backup.sh
|
||||
Enter password for /Volumes/Samsung BAR/b:
|
||||
@ -313,7 +315,3 @@ OK
|
||||
OK
|
||||
|
||||
👍
|
||||
|
||||
You should be careful to ensure the hash is not modified by an attacker, since this would allow [tampering with the backup](https://crypto.stackexchange.com/questions/83776/should-i-be-worried-about-xts-tampering-when-encrypting-backups-using-veracrypt/83782#83782). One good way to do this is to use an [HMAC](https://en.wikipedia.org/wiki/HMAC) hash instead of just hashing the backup, or to simply store a copy of the hash securely.
|
||||
|
||||
Putting the hash in another VeraCrypt container would be enough, assuming you use the standard XTS mode.
|
||||
|
Loading…
x
Reference in New Issue
Block a user