From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 4392169852 for ; Tue, 19 Jan 2021 15:18:01 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 32C441EA7F for ; Tue, 19 Jan 2021 15:17:31 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [212.186.127.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 692AA1EA76 for ; Tue, 19 Jan 2021 15:17:29 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 3430C46071 for ; Tue, 19 Jan 2021 15:17:29 +0100 (CET) From: Dylan Whyte To: pbs-devel@lists.proxmox.com Date: Tue, 19 Jan 2021 15:17:21 +0100 Message-Id: <20210119141721.23789-1-d.whyte@proxmox.com> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.020 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [wikipedia.org] Subject: [pbs-devel] [PATCH proxmox-backup] docs: clarify that client-server communication is secure X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jan 2021 14:18:01 -0000 This clarifies the fact that all communication between client and server uses TLS for secure communication. Signed-off-by: Dylan Whyte --- docs/faq.rst | 9 ++++++--- docs/introduction.rst | 16 +++++++++------- 2 files changed, 15 insertions(+), 10 deletions(-) diff --git a/docs/faq.rst b/docs/faq.rst index e0051859..8c41b36f 100644 --- a/docs/faq.rst +++ b/docs/faq.rst @@ -53,9 +53,12 @@ checksums. This manifest file is used to verify the integrity of each backup. When backing up to remote servers, do I have to trust the remote server? ------------------------------------------------------------------------ -Proxmox Backup Server supports client-side encryption, meaning your data is -encrypted before it reaches the server. Thus, in the event that an attacker -gains access to the server, they will not be able to read the data. +Proxmox Backup Server transfers data via `Transport Layer Security (TLS) +`_ and additionally +supports client-side encryption. This means that data is transferred securely +and can be encrypted before it reaches the server. Thus, in the event that an +attacker gains access to the server or any point of the network, they will not +be able to read the data. .. note:: Encryption is not enabled by default. To set up encryption, see the `Encryption diff --git a/docs/introduction.rst b/docs/introduction.rst index 20c29602..8df1f691 100644 --- a/docs/introduction.rst +++ b/docs/introduction.rst @@ -14,11 +14,12 @@ It supports deduplication, compression, and authenticated encryption (AE_). Using :term:`Rust` as the implementation language guarantees high performance, low resource usage, and a safe, high-quality codebase. -Proxmox Backup uses state of the art cryptography for client communication and -backup content :ref:`encryption `. Encryption is done on the -client side, making it safer to back up data to targets that are not fully -trusted. - +Proxmox Backup uses state of the art cryptography for both client-server +communication and backup content :ref:`encryption `. All +client-server communication uses `TLS +`_, and backup data can +be encrypted on the client-side before sending, making it safer to back up data +to targets that are not fully trusted. Architecture ------------ @@ -65,8 +66,9 @@ Main Features several gigabytes of data per second. :Encryption: Backups can be encrypted on the client-side, using AES-256 in - Galois/Counter Mode (GCM_) mode. This authenticated encryption (AE_) mode - provides very high performance on modern hardware. + Galois/Counter Mode (GCM_). This authenticated encryption (AE_) mode + provides very high performance on modern hardware. In addition to client-side + encryption, all data is transferred via a secure TLS connection. :Web interface: Manage the Proxmox Backup Server with the integrated, web-based user interface. -- 2.20.1