Integrating Google Authenticator with SSH logins
Finalizing
Once a secret key has been generated for every user that will need to use SSH, you must remove the nullok
option to enforce MFA. As a critical step before continuing, you must test the google-authenticator
module to make sure it is working on your system, as well as confirm that all existing users have set up secret keys and Google Authenticator on their devices. Once this step is complete, in /etc/pam.d/sshd
, change:
auth required pam_google_authenticator.so nullok
to:
auth required pam_google_authenticator.so
Then reload sshd
:
# systemctl reload sshd
Adding New Users
If you periodically add new users to the server that require SSH, these users will need to generate a key via a direct console login. If a console login is not feasible (e.g., servers running in a cloud service), then a temporary key will need to be generated by the system administrator or ideally by a user creation script. An administrator can generate a temporary key for a new user with the code in Listing 1.
Listing 1
Generating a Temporary Key
# su - new_user $ google-authenticator $ exit
Once generated, you then share the temporary secret key, QR code, or plaintext key with the user. The new user will ideally need to rerun key generation on their first login, which you can enforce with various methods such as using a flag file for new users.
Flag File Enforcement
The /etc/skel
directory contains default shell profiles and configurations that are copied into users' home directories on account creation. You will need to update /etc/skel/.profile
to check for a flag file. Flag files are empty files that are often used in shell scripts to determine how the script should behave. Append the if
block in Listing 2 to /etc/skel/.profile
.
Listing 2
Modify /etc/skel/.profile
# Run google-authenticator if a flag file exists. if [ -f $HOME/.first_login ] then google-authenticator rm -f $HOME/.first_login fi
The modification from Listing 2 will check if the flag file $HOME/.first_login
exists. If so, it will run google-authenticator
and then delete the flag file. When new users are added to the server by the administrator, the administrator can manually create the flag file in the new user's home directory with the commands in Listing 3.
Listing 3
Adding a New User and Creating a Flag
# useradd -m new_user # passwd new_user # su - new_user $ google-authenticator $ exit # touch /home/new_user/.first_login
To optionally automate this, you could create an empty flag file inside of /etc/skel
:
# touch /etc/skel/.first_login
By having the flag file inside of /etc/skel
, the flag file will be placed in the new user's home directory automatically, so the administrator will not need to touch
the flag file after creating the account.
« Previous 1 2 3 4 Next »
Buy this article as PDF
(incl. VAT)
Buy Linux Magazine
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.
News
-
Canonical Releases Ubuntu 24.04
After a brief pause because of the XZ vulnerability, Ubuntu 24.04 is now available for install.
-
Linux Servers Targeted by Akira Ransomware
A group of bad actors who have already extorted $42 million have their sights set on the Linux platform.
-
TUXEDO Computers Unveils Linux Laptop Featuring AMD Ryzen CPU
This latest release is the first laptop to include the new CPU from Ryzen and Linux preinstalled.
-
XZ Gets the All-Clear
The back door xz vulnerability has been officially reverted for Fedora 40 and versions 38 and 39 were never affected.
-
Canonical Collaborates with Qualcomm on New Venture
This new joint effort is geared toward bringing Ubuntu and Ubuntu Core to Qualcomm-powered devices.
-
Kodi 21.0 Open-Source Entertainment Hub Released
After a year of development, the award-winning Kodi cross-platform, media center software is now available with many new additions and improvements.
-
Linux Usage Increases in Two Key Areas
If market share is your thing, you'll be happy to know that Linux is on the rise in two areas that, if they keep climbing, could have serious meaning for Linux's future.
-
Vulnerability Discovered in xz Libraries
An urgent alert for Fedora 40 has been posted and users should pay attention.
-
Canonical Bumps LTS Support to 12 years
If you're worried that your Ubuntu LTS release won't be supported long enough to last, Canonical has a surprise for you in the form of 12 years of security coverage.
-
Fedora 40 Beta Released Soon
With the official release of Fedora 40 coming in April, it's almost time to download the beta and see what's new.