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 F03F49EA23 for ; Wed, 7 Jun 2023 10:49:39 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D34563E716 for ; Wed, 7 Jun 2023 10:49:39 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (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 for ; Wed, 7 Jun 2023 10:49:39 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id C9D7B41DCA for ; Wed, 7 Jun 2023 10:49:38 +0200 (CEST) From: Wolfgang Bumiller To: pve-devel@lists.proxmox.com Date: Wed, 7 Jun 2023 10:49:37 +0200 Message-Id: <20230607084937.91983-1-w.bumiller@proxmox.com> X-Mailer: git-send-email 2.39.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.128 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: [pve-devel] [PATCH docs] user management: document TFA lockout X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jun 2023 08:49:40 -0000 Signed-off-by: Wolfgang Bumiller --- pveum.adoc | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/pveum.adoc b/pveum.adoc index 6a0ad17..707e87d 100644 --- a/pveum.adoc +++ b/pveum.adoc @@ -579,6 +579,30 @@ documentation for how to use the https://www.yubico.com/products/services-software/yubicloud/[YubiCloud] or https://developers.yubico.com/Software_Projects/Yubico_OTP/YubiCloud_Validation_Servers/[host your own verification server]. +[[pveum_tfa_lockout]] +Limits and lockout of Two-Factor Authentication +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +A second factor is meant to protect users if their password is somehow leaked +or guessed. However, some factors could still be broken by brute force. For +this reason, users will be locked out after too many failed 2nd factor login +attempts. + +For TOTP 8 failed attempts will disable the user's TOTP factors. They are +unlocked when logging in with a recovery key. If TOTP was the only available +factor, admin intervention is required, and it is highly recommended to require +the user to change their password immediately. + +Since FIDO2/Webauthn and recovery keys are less susceptible to brute force +attacks, the limit there is higher, but block all second factors for an hour +when exceeded. + +An admin can unlock a user's Two-Factor Authentication at any time via the user +list in the UI or the command line: + +[source,bash] + pveum user tfa unlock joe@pve + [[pveum_user_configured_totp]] User Configured TOTP Authentication ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- 2.39.2