From 392ae32644ae021e5971071235573f7cf533531b Mon Sep 17 00:00:00 2001 From: DatuX Date: Mon, 22 May 2023 13:18:55 +0200 Subject: [PATCH] Updated Encryption (markdown) --- Encryption.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Encryption.md b/Encryption.md index aabd9dd..1244e72 100644 --- a/Encryption.md +++ b/Encryption.md @@ -12,7 +12,7 @@ Basically you dont have to do anything or worry about anything. Things get more interesting if you want to change the encryption-state of a dataset during transfer: * If you want to decrypt encrypted datasets before sending them, you should use the `--decrypt` option. Datasets will then be stored plain at the target. -* If you want to encrypt plain datasets when they are received, you should use the `--encrypt` option. Datasets will then be stored encrypted at the target. (Datasets that are already encrypted will still be sent over unaltered in raw-mode.) +* If you want to encrypt plain datasets when they are received, you should use the `--encrypt` option. Datasets will then be stored encrypted at the target. Datasets that are already encrypted will still be sent over unaltered in raw-mode. * If you also want re-encrypt encrypted datasets with the target-side encryption you can use both options. Note 1: 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.