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
-
PipeWire 1.0 Officially Released
PipeWire was created to take the place of the oft-troubled PulseAudio and has finally reached the 1.0 status as a major update with plenty of improvements and the usual bug fixes.
-
Rocky Linux 9.3 Available for Download
The latest version of the RHEL alternative is now available and brings back cloud and container images for ppc64le along with plenty of new features and fixes.
-
Ubuntu Budgie Shifts How to Tackle Wayland
Ubuntu Budgie has yet to make the switch to Wayland but with a change in approaches, they're finally on track to making it happen.
-
TUXEDO's New Ultraportable Linux Workstation Released
The TUXEDO Pulse 14 blends portability with power, thanks to the AMD Ryzen 7 7840HS CPU.
-
AlmaLinux Will No Longer Be "Just Another RHEL Clone"
With the release of AlmaLinux 9.3, the distribution will be built entirely from upstream sources.
-
elementary OS 8 Has a Big Surprise in Store
When elementary OS 8 finally arrives, it will not only be based on Ubuntu 24.04 but it will also default to Wayland for better performance and security.
-
OpenELA Releases Enterprise Linux Source Code
With Red Hat restricting the source for RHEL, it was only a matter of time before those who depended on that source struck out on their own.
-
StripedFly Malware Hiding in Plain Sight as a Cryptocurrency Miner
A rather deceptive piece of malware has infected 1 million Windows and Linux hosts since 2017.
-
Experimental Wayland Support Planned for Linux Mint 21.3
As with most Linux distributions, the migration to Wayland is in full force. While some distributions have already made the move, Linux Mint has been a bit slower to do so.
-
Window Maker Live 0.96.0-0 Released
If you're a fan of the Window Maker window manager, there's a new official release of the Linux distribution that champions the old-school user interface.