From b981cfbb548ae087ed226e855ed98251cdf82b6f Mon Sep 17 00:00:00 2001 From: Joey Hafner Date: Tue, 13 Feb 2024 11:22:00 -0800 Subject: [PATCH] Update docs for removing 2FA --- docs/Security.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/Security.md b/docs/Security.md index 45d011c..a78a068 100644 --- a/docs/Security.md +++ b/docs/Security.md @@ -117,7 +117,8 @@ https://www.digitalocean.com/community/tutorials/how-to-set-up-multi-factor-auth Some use cases (such as programmatic access) demand 2FA be disabled. Some day we'll figure out how to allow specific keys to bypass the 2FA requirement. But until then, -Edit the file `/etc/ssh/sshd_config` as root. Set `UsePAM` from `yes` to `no`. +1. Edit the file `/etc/pam.d/sshd` and comment out the line `auth sufficient pam_google_authenticator.so nullok` +2. Edit the file `/etc/ssh/sshd_config` and find the `AuthenticationMethods` configuration. Replace the value `publickey,keyboard-interactive` with `publickey`. ### SSH Key Management The process for managing SSH keys should work as follows: