From b0710274ca2595c7bf37a4057243d281bc1c9195 Mon Sep 17 00:00:00 2001 From: DatuX Date: Tue, 26 Sep 2023 11:43:26 +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 a00b60c..2b63008 100644 --- a/Encryption.md +++ b/Encryption.md @@ -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)