我正在尝试配置我的 SSHD 以使用 FreeRadius 对用户进行身份验证。FreeRadius 服务器需要首先使用 Google Authenticator 请求有效的 OTP，然后验证系统帐户密码。
如果我将 Radius 服务器设置为仅有的使用 Google Authenticator，但当我添加询问系统帐户密码的额外步骤时，Google Authenticator 令牌每次都会失败。我认为我的问题出在我的 PAM 配置上，但我不明白我做错了什么。
我将运行 SSHD 的服务器称为“客户端”服务器，将 FreeRadius 服务器称为“半径”服务器。
这是我的客户端：/etc/pam.d/sshd
#%PAM-1.0
auth required pam_sepermit.so
auth required pam_radius_auth.so debug prompt=token
#auth include password-auth
auth include postlogin
account required pam_nologin.so
account include password-auth
account sufficient pam_radius_auth.so
password include password-auth
# pam_selinux.so close should be the first session rule
session required pam_selinux.so close
session required pam_loginuid.so
# pam_selinux.so open should only be followed by sessions to be executed in the user context
session required pam_selinux.so open env_params
session optional pam_keyinit.so force revoke
session include password-auth
session include postlogin
我还在客户端：/etc/ssh/sshd_config 中启用了质询/响应身份验证，并使用以下行：
ChallengeResponseAuthentication yes
这是我在 radius 服务器上的 /etc/pam.d/radiusd 配置：
#%PAM-1.0
auth requisite pam_google_authenticator.so
auth include password-auth
account required pam_nologin.so
account include password-auth
password include password-auth
session include password-auth
#@include common-auth
#@include common-account
#@include common-password
#@include common-session
为了让您能够跟踪该链，这里是 radius 服务器上的 /etc/pam.d/password-auth 文件：
#%PAM-1.0
# This file is auto-generated.
# User changes will be destroyed the next time authconfig is run.
auth required pam_env.so
auth sufficient pam_unix.so nullok try_first_pass
auth requisite pam_succeed_if.so uid >= 1000 quiet_success
auth required pam_deny.so
account required pam_unix.so
account sufficient pam_localuser.so
account sufficient pam_succeed_if.so uid < 1000 quiet
account required pam_permit.so
password requisite pam_pwquality.so try_first_pass local_users_only retry=3 authtok_type=
password sufficient pam_unix.so sha512 shadow nullok try_first_pass use_authtok
password required pam_deny.so
session optional pam_keyinit.so revoke
session required pam_limits.so
-session optional pam_systemd.so
session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid
session required pam_unix.so
这种方式应该这样工作：客户端服务器只需要 radius 服务器接受即可接受登录，但 radius 服务器需要使用 GoogleAuthenticator 的 OTP 和本地 pam_unix 密码才能接受。这就是我想要的。
奇怪的是，当我在 radius 服务器 /etc/pam.d/radiusd 文件上注释掉以下行时：
auth include password-auth
然后我可以登录到客户端服务器，它会提示我输入 GoogleAuthenticator 令牌。当我这样做时，一切都正常。我从手机获取的 OTP 被接受，请求被发送到 radius，它返回到客户端服务器，并让我进入。
但是，如果取消注释上述行，系统会要求我输入 GoogleAuthenticator 令牌，每次输入时都会失败。奇怪的是，系统要求我输入 OTP 令牌 4 次，然后要求我输入系统帐户密码，然后说输入失败。有人能帮我解决这个问题吗？
这是我尝试使用时“radiusd -X”的调试输出两个都GoogleAuthenticator 令牌和 unix 密码：
Received Access-Request Id 112 from client:48253 to radius:1812 length 94
User-Name = ‘bob’
User-Password = '146963'
NAS-IP-Address = client
NAS-Identifier = 'sshd'
NAS-Port = 9148
NAS-Port-Type = Virtual
Service-Type = Authenticate-Only
Calling-Station-Id = ‘xxx.xxx.xxx.xxx’
(0) Received Access-Request packet from host 192.168.20.51 port 48253, id=112, length=94
(0) User-Name = ‘bob’
(0) User-Password = '146963'
(0) NAS-IP-Address = xxx.xxx.xxx.xxx
(0) NAS-Identifier = 'sshd'
(0) NAS-Port = 9148
(0) NAS-Port-Type = Virtual
(0) Service-Type = Authenticate-Only
(0) Calling-Station-Id = ‘xxx.xxx.xxx.xxx’
(0) # Executing section authorize from file /etc/raddb/sites-enabled/default
(0) authorize {
(0) filter_username filter_username {
(0) if (!&User-Name)
(0) if (!&User-Name) -> FALSE
(0) if (&User-Name =~ / /)
(0) if (&User-Name =~ / /) -> FALSE
(0) if (&User-Name =~ /@.*@/ )
(0) if (&User-Name =~ /@.*@/ ) -> FALSE
(0) if (&User-Name =~ /\\.\\./ )
(0) if (&User-Name =~ /\\.\\./ ) -> FALSE
(0) if ((&User-Name =~ /@/) && (&User-Name !~ /@(.+)\\.(.+)$/))
(0) if ((&User-Name =~ /@/) && (&User-Name !~ /@(.+)\\.(.+)$/)) -> FALSE
(0) if (&User-Name =~ /\\.$/)
(0) if (&User-Name =~ /\\.$/) -> FALSE
(0) if (&User-Name =~ /@\\./)
(0) if (&User-Name =~ /@\\./) -> FALSE
(0) } # filter_username filter_username = notfound
(0) [preprocess] = ok
(0) [chap] = noop
(0) [mschap] = noop
(0) [digest] = noop
(0) suffix : Checking for suffix after "@"
(0) suffix : No '@' in User-Name = “bob”, looking up realm NULL
(0) suffix : No such realm "NULL"
(0) [suffix] = noop
(0) eap : No EAP-Message, not doing EAP
(0) [eap] = noop
(0) files : users: Matched entry DEFAULT at line 198
(0) [files] = ok
(0) [expiration] = noop
(0) [logintime] = noop
(0) WARNING: pap : No "known good" password found for the user. Not setting Auth-Type
(0) WARNING: pap : Authentication will fail unless a "known good" password is available
(0) [pap] = noop
(0) } # authorize = ok
(0) Found Auth-Type = PAM
(0) # Executing group from file /etc/raddb/sites-enabled/default
(0) authenticate {
pam_pass: using pamauth string <radiusd> for pam.conf lookup
pam_pass: function pam_authenticate FAILED for <bob>. Reason: Authentication failure
(0) [pam] = reject
(0) } # authenticate = reject
(0) Failed to authenticate the user
(0) Using Post-Auth-Type Reject
(0) # Executing group from file /etc/raddb/sites-enabled/default
(0) Post-Auth-Type REJECT {
(0) attr_filter.access_reject : EXPAND %{User-Name}
(0) attr_filter.access_reject : --> bob
(0) attr_filter.access_reject : Matched entry DEFAULT at line 11
(0) [attr_filter.access_reject] = updated
(0) eap : Request didn't contain an EAP-Message, not inserting EAP-Failure
(0) [eap] = noop
(0) remove_reply_message_if_eap remove_reply_message_if_eap {
(0) if (&reply:EAP-Message && &reply:Reply-Message)
(0) if (&reply:EAP-Message && &reply:Reply-Message) -> FALSE
(0) else else {
(0) [noop] = noop
(0) } # else else = noop
(0) } # remove_reply_message_if_eap remove_reply_message_if_eap = noop
(0) } # Post-Auth-Type REJECT = updated
(0) Delaying response for 1 seconds
Waking up in 0.9 seconds.
(0) Sending delayed response
(0) Sending Access-Reject packet to host xxx.xxx.xxx.xxx port 48253, id=112, length=0
Sending Access-Reject Id 112 from xxx.xxx.xxx.xxx:1812 to xxx.xxx.xxx.xxx:48253
Waking up in 3.9 seconds.
(0) Cleaning up request packet ID 112 with timestamp +20
Ready to process requests
Received Access-Request Id 81 from xxx.xxx.xxx.xxx:45486 to xxx.xxx.xxx.xxx:1812 length 94
User-Name = ’bob’
User-Password = '146963'
NAS-IP-Address = xxx.xxx.xxx.xxx
NAS-Identifier = 'sshd'
NAS-Port = 9149
NAS-Port-Type = Virtual
Service-Type = Authenticate-Only
Calling-Station-Id = ‘xxx.xxx.xxx.xxx’
答案1
我找到了答案。问题出在 /etc/pam.d/password-auth 文件的 PAM 堆栈中。具体来说，是这一行：
auth sufficient pam_unix.so nullok try_first_pass
当时的情况是，google-authenticator 的令牌已被接受，但由于“try_first_pass”选项，pam_unix.so 试图使用该代码作为系统密码。我不知道为什么，但这导致整个身份验证链重新开始，要求输入 google-auth 密码。
摆脱“try_first_pass”选项可以解决问题并给我所需的行为。