You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Match User [REDACTED]
AuthenticationMethods keyboard-interactive
also changed ChallengeResponseAuthentication no to ChallengeResponseAuthentication yes
This setup works on other servers only difference config wise is sufficient is required in pam.d/sshd
The behavior originally looked to be DNS related but running a tcpdump on port 53 shows the module performing lookups fine.
Essentially what happens is after the keypress it looking to accept the key but does not log in eventually sshd times the connection out
I'm not sure if it's related but I have spun up a test server with the same network config and that works fine the only difference is the servers with issues have been converted from centOS 8 to alma linux via the alma deploy script.
Nothing shows up in the debug log when attempting to auth via ssh, hoping someone can share some additional troubleshooting steps that might narrow down the problem
Thanks in advance.
The text was updated successfully, but these errors were encountered:
Hi folks,
Having a strange issue getting the module setup for ssh.
So in testing I have added the following to pam.d/sshd
auth sufficient pam_yubico.so id=[REDACTED] debug authfile=/etc/yubico
And this to sshd_config
Match User [REDACTED]
AuthenticationMethods keyboard-interactive
also changed ChallengeResponseAuthentication no to ChallengeResponseAuthentication yes
This setup works on other servers only difference config wise is sufficient is required in pam.d/sshd
The behavior originally looked to be DNS related but running a tcpdump on port 53 shows the module performing lookups fine.
Essentially what happens is after the keypress it looking to accept the key but does not log in eventually sshd times the connection out
I'm not sure if it's related but I have spun up a test server with the same network config and that works fine the only difference is the servers with issues have been converted from centOS 8 to alma linux via the alma deploy script.
Nothing shows up in the debug log when attempting to auth via ssh, hoping someone can share some additional troubleshooting steps that might narrow down the problem
Thanks in advance.
The text was updated successfully, but these errors were encountered: