在Linux中为SSH设置双因素身份验证及取消

最新推荐文章于 2025-03-27 13:29:58 发布

原创最新推荐文章于 2025-03-27 13:29:58 发布 · 1.1k 阅读

31 ·

CC 4.0 BY-SA版权

文章标签：

#linux #ssh #运维

Linux 同时被 2 个专栏收录

36 篇文章

订阅专栏

ECS

31 篇文章

订阅专栏

重点配置(配置及取消)：

编辑SSH配置文件

sudo vim /etc/ssh/sshd_config

确保以下行被设置为 yes

ChallengeResponseAuthentication yes

UsePAM yes

若想取消，设置为：no

最后，重启sshd服务。

刨根问底：

1.同步Linux服务器时钟

同步linux时钟，默认动态验证码在30秒内有效，由于客户端和服务器可能会存在时间差，建议先同步时钟，防止和手机时间存在时间差导致无法登录

[root@knode1 ~]# ntpdate pool.ntp.org
5 Dec 23:00:32 ntpdate[6583]: step time server 84.16.73.33 offset -9.050575 sec

2.Linux主机安装Google Authenticator

本文使用Centos7系统实验，在终端执行以下命令，为你的Linux系统安装Google Authenticator插件

yum -y install epel-release # CentOS/RHEL sudo yum install google-authenticator # CentOS/RHEL

3.修改SSH配置

编辑SSH配置文件

sudo vi /etc/ssh/sshd_config

确保以下行被设置为 yes

ChallengeResponseAuthentication yes

UsePAM yes

保存并退出

4.Google Authenticator初始化

执行以下命令初始配置，为指定用户启动Google Authenticator的配置

[root@cxsdn ~]# google-authenticator Do you want authentication tokens to be time-based (y/n) y Warning: pasting the following URL into your browser exposes the OTP secret to Google: https://www.google.com/chart?chs=200x200&chld=M|0&cht=qr&chl=otpauth://totp/root@knode1%3Fsecret%3D55624OUOSZPCU5XZP64KSX2BKE%26issuer%3Dknode1 Your new secret key is: 55624OUOSZPCU5XZP64KSX2BKE #google身份验证上添加的key Your verification code is 340500 Your emergency scratch codes are: 41836466 27541454 93396333 53788584 26617777 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) y By default, a new token is generated every 30 seconds by the mobile app. #默认30s过期 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. This allows for a time skew of up to 30 seconds between authentication server and client. If you experience problems with poor time synchronization, you can increase the window from its default size of 3 permitted codes (one previous code, the current code, the next code) to 17 permitted codes (the 8 previous codes, the current code, and the 8 next codes). This will permit for a time skew of up to 4 minutes between client and server. Do you want to do so? (y/n) y 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) y