From 200fd3aa05174e109488f533d57db503d18ce25a Mon Sep 17 00:00:00 2001 From: David Steele Date: Fri, 4 Jan 2019 12:25:58 +0200 Subject: [PATCH] Clarify that encryption is always performed client-side. Suggested by Bruce Burdick. --- doc/xml/reference.xml | 2 +- doc/xml/release.xml | 16 ++++++++++++++++ doc/xml/user-guide.xml | 2 +- 3 files changed, 18 insertions(+), 2 deletions(-) diff --git a/doc/xml/reference.xml b/doc/xml/reference.xml index ea122aa82..341a2db94 100644 --- a/doc/xml/reference.xml +++ b/doc/xml/reference.xml @@ -477,7 +477,7 @@ + Note that encryption is always performed client-side even if the repository type (e.g. S3) supports encryption. none aes-256-cbc diff --git a/doc/xml/release.xml b/doc/xml/release.xml index 071996362..c5e7e0700 100644 --- a/doc/xml/release.xml +++ b/doc/xml/release.xml @@ -13,6 +13,17 @@ + + + + + + + +

Clarify that encryption is always performed client-side.

+
+
+
@@ -5994,6 +6005,11 @@ scrummyin + + Bruce Burdick + baburdick + + Camilo Aguilar c4milo diff --git a/doc/xml/user-guide.xml b/doc/xml/user-guide.xml index 7abb35b33..a67661d74 100644 --- a/doc/xml/user-guide.xml +++ b/doc/xml/user-guide.xml @@ -941,7 +941,7 @@
Configure Repository Encryption -

The repository will be configured with a cipher type and key to demonstrate encryption.

+

The repository will be configured with a cipher type and key to demonstrate encryption. Encryption is always performed client-side even if the repository type (e.g. S3) supports encryption.

It is important to use a long, random passphrase for the cipher key. A good way to generate one is to run: openssl rand -base64 48.