Secure your logins with two-factor authentication
Secure Remote Access
There's no dearth of tricks to harden an SSH connection. For example, you can change its default port and restrict access by IP addresses. The most commonly suggested mechanism is to switch to key-based authentication instead of passwords, but this still presents a single point of failure. To make it more difficult for an attacker to compromise an SSH connection, you can also enable two-factor authentication for remote logins (Figure 6).
The procedure for adding OTP-based logins to an SSH connection is similar to the one for local logins. The only difference is that you need to install and setup the Google Authenticator PAM module on the remote SSH machine instead of the local machine. Begin by SSHing into the remote server as the user you wish to protect such as ssh bodhi@remote-machine
.
Now open another SSH connection to the machine and use this second connection to make changes to SSH's configuration. When you restart the SSH service on the remote machine, it won't close open connections. So the first connection acts as a fail-safe and ensures you won't lock yourself out in case of any accidental misconfiguration.
After you've logged into the remote machine, follow the steps described earlier to first install the Google Authenticator PAM module and then use the helper script to generate the 16 digit key for the remote user. Then add the details of this remote SSH user in the Google Authenticator mobile app.
Next, you can edit SSH's PAM configuration file on this remote machine with nano /etc/pam.d/sshd
. Scroll down to the bottom and add the following lines to the file:
# Secure SSH with OTPs auth required pam_google_authenticator.so nullok
Just like earlier, nullok
tells PAM that this authentication method is optional. This allows users without a Google Authenticator key to still log in using their SSH password. Remember that this is just a fail safe to prevent you from being locked out in case something goes wrong with the setup process. However, once you've tested it successfully, generate a key for all SSH users and delete nullok
from the end of this line to make logins via OTP mandatory.
After editing SSH's PAM file, it's time to configure SSH to support this kind of authentication. Open the SSH configuration file for editing with:
nano /etc/ssh/sshd_config
Look for the line that reads ChallengeResponseAuthentication
and change its value from no to yes. If the line doesn't exist, make sure you add it manually. Save and close the file, and then restart SSH to reload the configuration files with:
systemctl restart sshd.service
When you now re-establish the SSH connection, in addition to the remote user's password, you'll also be prompted for the Google Authenticator code.
Two-factor authentication is relatively straightforward to roll out but it takes some getting used to. However, you can rest easy knowing that you've increased the security of your computer by making it virtually impossible for crackers to brute force their way into your home directory.
Infos
- Google Authenticator: https://en.wikipedia.org/wiki/Google_Authenticator
- FreeOTP app: https://freeotp.github.io/
- The TOTP protocol: https://en.wikipedia.org/wiki/Time-based_One-time_Password_Algorithm
« Previous 1 2
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
-
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.
-
New Pentesting Distribution to Compete with Kali Linux
SnoopGod is now available for your testing needs
-
Juno Computers Launches Another Linux Laptop
If you're looking for a powerhouse laptop that runs Ubuntu, the Juno Computers Neptune 17 v6 should be on your radar.