Updated Encryption (markdown)

DatuX
2023-09-26 11:43:26 +02:00
parent 195331a759
commit b0710274ca

@ -20,7 +20,7 @@ Things get more interesting if you want to change the encryption-state of a data
* The --encrypt option will rely on inheriting encryption parameters from the parent datasets on the target side. You are responsible for setting those up and loading the keys. So --encrypt is no guarantee for encryption: If you dont set it up, it cant encrypt. (and will store the data unencrypted)
* --encrypt will be ignored for datasets that are already encrypted: These are transferred in raw mode.
* --encrypt will be ignored for datasets that are already encrypted: These are transferred in raw mode, unless you specify --decrypt as well.
* Decide what you want at an early stage: If you change the --encrypt or --decrypt parameter after the inital sync you might get weird and wonderfull errors. (nothing dangerous)