Difference between revisions of "Two Factors Authentication With OpenSSH"

From Alpine Linux
Jump to: navigation, search
Line 1: Line 1:
== Using Google Authenticator ==
== Using Google Authenticator ==
{{cmd|apk add google-authenticator openssh-server-pam}}
{{cmd|# apk add google-authenticator openssh-server-pam}}
{{cmd|cat /etc/ssh/sshd_config}}
{{cmd|# cat /etc/ssh/sshd_config}}
AuthenticationMethods publickey,keyboard-interactive
AuthenticationMethods publickey,keyboard-interactive
Line 11: Line 11:
{{Note|This configuration does NOT allow password authentication globally}}
{{Note|This configuration does NOT allow password authentication globally}}
{{cmd|cat /etc/pam.d/sshd #create the file if needed}}
{{cmd|# cat /etc/pam.d/sshd #create the file if needed}}
account include base-account
account include base-account

Revision as of 17:04, 7 December 2018

Using Google Authenticator

# apk add google-authenticator openssh-server-pam

# cat /etc/ssh/sshd_config

AuthenticationMethods publickey,keyboard-interactive
ChallengeResponseAuthentication yes
PermitRootLogin yes
UsePAM yes
Note: This configuration does NOT allow password authentication globally

# cat /etc/pam.d/sshd #create the file if needed

account		include				base-account

auth		required			pam_env.so
auth		required			pam_nologin.so	successok
auth		include				google-authenticator

Time-based One Time Password authentication (TOTP RFC 6238)

As user root:


Note: Please take note of <secret>
Do you want authentication tokens to be time-based (y/n) y
Your new secret key is: <secret>
Your verification code is <pruned>
Your emergency scratch codes are:

Do you want me to update your "/root/.google_authenticator" file? (y/n) y

Do you want to disallow multiple uses of the same authentication
token? This restricts you to one login about every 30s, but it increases
your chances to notice or even prevent man-in-the-middle attacks (y/n) n

By default, tokens are good for 30 seconds. In order to compensate for
possible time-skew between the client and the server, we allow an extra
token before and after the current time. If you experience problems with
poor time synchronization, you can increase the window from its default
size of +-1min (window size of 3) to about +-4min (window size of
17 acceptable tokens).
Do you want to do so? (y/n) n

If the computer that you are logging into isn't hardened against brute-force
login attempts, you can enable rate-limiting for the authentication module.
By default, this limits attackers to no more than 3 login attempts every 30s.
Do you want to enable rate-limiting (y/n) n
Tip: You might want to answer differently at questions 2, 3 and 4 based on your paranoia's level and firewall settings :)

Re-run google-authenticator for each user that needs to login via SSH. Don't forget to include .google_authenticator files in your LBU if you're running from RAM.


Download Google Authenticator app from your App Store. Startup Google Authenticator app and enter manually your <secret> key.


ssh -v root@yourbox

You should see the last lines saying:

Authenticated with partial success.
debug1: Authentications that can continue: keyboard-interactive
debug1: Next authentication method: keyboard-interactive
Verification code: 

Authenticated with partial success means that pubkey authentication was successfull and now the verifier is asking for the verification code generated from the Google Authenticator app.