macOS
brew install google-authenticator-libpamprovider-native install command
brew / rang 5378
Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de google-authenticator-libpam pour les workflows d'agents IA.
installation
brew install google-authenticator-libpamprovider-native install command
aperçu
PAM module for two-factor authentication
historique
google-authenticator-libpam is Google's PAM module and setup utility for adding HOTP or TOTP second-factor authentication to Unix login flows such as SSH and OpenVPN. Its package significance is unusually high for a small C/PAM project because it bridges standard one-time-password algorithms, the Google Authenticator app ecosystem, and distribution-level authentication stacks.
The project implements a PAM module named pam_google_authenticator and a google-authenticator setup binary. The README describes it as an example PAM module for two-factor authentication to servers via SSH, OpenVPN, and similar services, and explicitly scopes it away from logging into Google or other TOTP/HOTP services.
The implementation is grounded in the HOTP and TOTP standards. RFC 4226 defined HMAC-based one-time passwords in 2005, and RFC 6238 extended HOTP with a time-based moving factor in 2011. The project's README cites both standards as the algorithms behind its one-time codes.
The GitHub repository was created in November 2016 under Google's organization, and Git tags show 1.03 through 1.11 release labels. The man page documents the PAM module interface, default secret-file behavior, security notes, and deployment options.
The package is widely packaged under names such as google-authenticator-libpam, google-authenticator, and libpam-google-authenticator. The batch metadata records Homebrew, Alpine, Debian, Fedora, Nix, Ubuntu, and openSUSE-family package names, and Homebrew's formula page documents SSH PAM configuration snippets.
Its adoption comes from fitting an existing Unix security boundary: administrators can add an auth required pam_google_authenticator.so line to PAM configuration and let users enroll per-account secrets, rather than deploying a separate authentication server.
Because PAM is distribution- and service-sensitive, the project also exposes rollout controls such as nullok for users without a secret file, secret= for nonstandard secret locations, user= for alternate file access, owner and permission checks, time-skew handling, HOTP counter behavior, and combined password-code prompting.
A user typically runs google-authenticator to create ~/.google_authenticator. The setup can display a QR code when libqrencode is available, or provide a URL or alphanumeric secret that can be entered into an authenticator app.
An administrator enables the PAM module in a service configuration, commonly with an auth line for pam_google_authenticator.so. The module then prompts for a one-time code in addition to the normal password, using either time-based TOTP or counter-based HOTP depending on user setup and options.
The man page emphasizes that the secret file is per account, defaults to .google_authenticator in the user's home directory, and must satisfy ownership and permission checks unless explicitly relaxed.
For package nerds, google-authenticator-libpam is a classic example of a small library package with outsized operational consequences. Packaging has to put a PAM shared object in the right security module path, install a user enrollment binary, and often provide service-specific post-install guidance.
It is also a good reminder that authentication packages are not just CLIs. Their paths, file permissions, PAM control flags, and distro integration details can determine whether users are protected, locked out, or silently bypassing a second factor.
posture de sécurité
narrow executable package without higher-risk signals.
risque vert · confiance faible · appliance
Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des plugins.
local files
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Credential-bearing paths to review before unattended agent runs.
~/.google_authenticatorexécutables
| Commande | Type | Exposition | Note |
|---|---|---|---|
google-authenticator | exécutable | exécutable indexé | Découvert depuis l'index local des exécutables. |
fraîcheur
Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.
métadonnées d'installation
| Clé du paquet | brew:google-authenticator-libpam |
|---|---|
| Version | 1.11 |
| Gestionnaire de paquets | Homebrew |
| Page d'accueil | https://github.com/google/google-authenticator-libpam |
| Dépôt | https://github.com/google/google-authenticator-libpam |
| Bouteille | non enregistré |
| Service | aucun déclaré |
piste source
Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.
View the package source record on GitHub.