second-factor authentication via Duo login
provides secondary authentication via the
Duo authentication service, executing the user's login shell or command only
The following options are available:
- Specify an alternate configuration file to load. Default is
- Debug mode; send logs to stderr instead of syslog.
- Specify the remote IP address for this login (normally
taken from the
environment variable, if set).
- Specify an alternate Duo user to authenticate as.
is installed setuid root (the
default), these options are only available to the super-user.
After successful Duo authentication, the user's login shell is invoked, or if an
is specified, it will be executed via the user's shell with a -c option.
The INI-format configuration file must have a
” section with the following
- Duo API host (required).
- Duo integration key (required).
- Duo secret key (required).
- If specified, Duo authentication is required only for users
whose primary group or supplementary group list matches one of the
space-separated pattern-lists (see
- On service or configuration errors that prevent Duo
authentication, fail “
access) or “
secure” (deny access).
Default is “
- Send command to be approved via Duo Push authentication.
Default is “
- Use the specified HTTP proxy, same format as the HTTP_PROXY
- Upon successful first-factor authentication, automatically
send a login request to the primary second-factor (usually Duo Push). Can
no”. Default is
- Print the contents of
/etc/motd to screen after a successful login.
Either "yes" or "no." Default is "no".
- Number of login attempts a user gets. Default is 3. If
using autopush, it is recommended to set prompts to 1.
- Look for factor selection or passcode in the DUO_PASSCODE
environment variable, before prompting the user. Can override autopush.
Default is "no".
- If unable to determine the authentication users's IP
address, fallback on the IP address of the server. Default is
- Set to the number of seconds to wait for HTTPS responses
from Duo Security. If Duo Security takes longer than the configured number
of seconds to respond to the preauth API call, the configured failmode is
triggered. Other network operations such as DNS resolution, TCP connection
establishment, and the SSL handshake have their own independent timeout
and retry logic. Default is 0, which disables the HTTPS timeout.
An example configuration file:
host = api-deadbeef.duosecurity.com
ikey = SI9F...53RI
skey = 4MjR...Q2NmRiM2Q1Y
pushinfo = yes
autopush = yes
If installed setuid root (the default), login_duo
performs Duo authentication as a dedicated privilege separation user,
requiring that the configuration file be owned and readable only by this user.
consists of zero or more non-whitespace
characters, ‘*’ (a wildcard that matches zero or more
characters), or ‘?’ (a wildcard that matches exactly one
is a comma-separated list of
patterns. Patterns within pattern-lists may be negated by preceding them with
an exclamation mark (‘!’). For example, to specify Duo
authentication for all users (except those that are also admins), and for
groups = users,!wheel,!*admin
can be enabled system-wide by specifying
its full path as a ForceCommand
to capture any SSH remote login
(including subsystems, remote commands, and interactive login):
Similarly, a group of administrators could require two-factor authentication for
login to a shared root account by specifying
as the forced command for each public
key in ~root/.ssh/authorized_keys
command="/usr/local/sbin/login_duo -f alice"
ssh-rsa AAAAB2...19Q== email@example.com
command="/usr/local/sbin/login_duo -f bob"
ssh-dss AAAAC3...51R== firstname.lastname@example.org
A user without root access could configure their own account to require Duo
authentication via the same
forced command mechanism
and a user-installed (non-setuid) login_duo
- Default configuration file path
was written by
When used to protect remote SSH access, only interactive sessions support
interactive Duo login. For scp(1)
and other ssh(1)
automatically tries the user's default
out-of-band factor (smartphone push or voice callback) and disables real-time
login progress reporting to provide a clean shell environment.