pam_authyo PAM module for SSH andDownload: the latest packages are on your Authyo dashboard download page. Debian/Ubuntu: authyo-gatekeeper_1.1.6-1_amd64.debRHEL/Rocky/Alma/Amazon Linux/Fedora: authyo-gatekeeper-1.1.6-1.x86_64.rpm
| Change | What it means for you |
|---|---|
| Never-stuck sign-in (anti-lockout) | When pam_authyo can't run the OTP step, your SSH login completes with your normal password instead of being denied. |
| No-contact no longer locks you out | A box with no / misconfigured contacts previously denied login. It now falls through to password auth. |
| Outage-safe | An Authyo outage or an unverifiable server policy also fall through to password (overrides the fail-closed policy). |
pam_authyo now guarantees a way in whenever it cannot perform the OTPignore), instead of failing the login:Behavior change to be aware of: previously, a server with no deliverable
contact returned an authentication error (a lockout). As of 1.1.6 that server
steps aside to password auth instead. If you relied on that hard failure, see
Strict mode below.
pam_authyo never authenticates you by itself. It only drops the OTPauth required
pam_authyo.so after your password module, as in the install guide.)/etc/authyo/gatekeeper.conf:{
"policy": {
"neverLockOut": false // strict: fail closed when OTP can't run
// ... your other policy settings ...
}
}sudo authyo-configure --test and confirm you can still get in from atrue (never-stuck).Note: Team Login is a Windows-only feature and does not apply to Linux SSH.
sudo apt install ./authyo-gatekeeper_1.1.6-1_amd64.debsudo dnf install ./authyo-gatekeeper-1.1.6-1.x86_64.rpmneverLockOut defaults to true, so an existinggatekeeper.conf without the key automatically gets the never-stuck behavior.sudo authyo-configure --test + a second terminal) before closing your currentR — resend (tries your next channel)B — I have a backup code (or paste XXXX-XXXX-XXXX directly)neverLockOut is set to false).