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 2C8A267A2B for ; Tue, 10 Nov 2020 12:05:11 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 22E451F8BC for ; Tue, 10 Nov 2020 12:05:11 +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)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 5A29F1F8B3 for ; Tue, 10 Nov 2020 12:05:09 +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 1A9EA46054 for ; Tue, 10 Nov 2020 12:05:09 +0100 (CET) From: Dylan Whyte To: pbs-devel@lists.proxmox.com Date: Tue, 10 Nov 2020 12:04:56 +0100 Message-Id: <20201110110456.21178-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.022 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 Subject: [pbs-devel] [PATCH docs] encryption: add best practice for storing master key 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, 10 Nov 2020 11:05:11 -0000 Further clarify that the paperkey should be a last resort recovery option, after a password manager and usb drive. Signed-off-by: Dylan Whyte --- docs/backup-client.rst | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/docs/backup-client.rst b/docs/backup-client.rst index 1ef42898..125c1fbc 100644 --- a/docs/backup-client.rst +++ b/docs/backup-client.rst @@ -367,11 +367,16 @@ To set up a master key: and needs to be restored, this will not be possible as the encryption key will be lost along with the broken system. -In preparation for the worst case scenario, you should consider keeping a paper -copy of your master key locked away in a safe place. The ``paperkey`` subcommand -can be used to create a QR encoded version of your master key. The following -command sends the output of the ``paperkey`` command to a text file, for easy -printing. +It is recommended that you keep your master key safe, but easily accessible, in +order for quick disaster recovery. For this reason, the best place to store it +is in your password manager, where it is immediately recoverable. As a backup to +this, you should also save the key to a USB drive and store that in a secure +place. This way, it is detached from any system, but is still easy to recover +from, in case of emergency. Finally, in preparation for the worst case scenario, +you should also consider keeping a paper copy of your master key locked away in +a safe place. The ``paperkey`` subcommand can be used to create a QR encoded +version of your master key. The following command sends the output of the +``paperkey`` command to a text file, for easy printing. .. code-block:: console -- 2.20.1