# google-authenticator-libpam を Homebrew, zypper, apk, dnf, Nix, apt でインストール

google-authenticator-libpam のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。

## インストール

```sh
sudo av install brew:google-authenticator-libpam
```

追加のインストールコマンド:

### macOS

- Homebrew (100%):

```sh
brew install google-authenticator-libpam
```

  証拠: local Homebrew formula metadata

### Linux

- zypper (92%):

```sh
sudo zypper install google-authenticator-libpam
```

  証拠: openSUSE Tumbleweed package metadata: google-authenticator-libpam from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst

- apk (92%):

```sh
sudo apk add google-authenticator
```

  証拠: Alpine Linux edge package indexes: google-authenticator from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz

- dnf (92%):

```sh
sudo dnf install google-authenticator
```

  証拠: Fedora Rawhide package metadata: google-authenticator from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst

- Nix (92%):

```sh
nix profile install nixpkgs#google-authenticator
```

  証拠: nixpkgs package indexes: pkgs/by-name/go/google-authenticator/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

- Debian apt (92%):

```sh
sudo apt install libpam-google-authenticator
```

  証拠: Debian stable package indexes: libpam-google-authenticator from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz

## パッケージ情報

- **パッケージキー:** brew:google-authenticator-libpam
- **パッケージマネージャ:** Homebrew
- **バージョン:** 1.11
- **ソース概要:** PAM module for two-factor authentication
- **ホームページ:** <https://github.com/google/google-authenticator-libpam>
- **リポジトリ:** <https://github.com/google/google-authenticator-libpam>
- **生成日時:** 2026-08-03T19:37:03+00:00

## 実行可能ファイル

- google-authenticator (エイリアス)

## インストール挙動

- Bottle: 利用不可

## バージョンと鮮度

- ページ生成日: 2026-08-03
- マネージャ版: 1.11
## プロジェクトの歴史と使われ方

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.

### タイムライン

- 2005: RFC 4226 publishes HOTP.
- 2011: RFC 6238 publishes TOTP as a time-based extension of HOTP.
- 2016-11: Google GitHub repository created.
- 2016-2026: Git tags show 1.03 through 1.11 release labels.
- 2026: README and man page document PAM setup, ~/.google_authenticator secrets, HOTP/TOTP behavior, and security-sensitive module options.

### Related projects

- Google Authenticator mobile apps generate compatible one-time codes for enrolled secrets.
- Linux-PAM and service PAM configurations such as sshd and OpenVPN are the integration surfaces for the module.
- pam_oath, FreeOTP, oathtool, and other OATH-compatible tooling occupy adjacent HOTP/TOTP authentication space.

### ソース

- <https://api.github.com/repos/google/google-authenticator-libpam>
- <https://formulae.brew.sh/formula/google-authenticator-libpam>
- <https://github.com/google/google-authenticator-libpam>
- <https://raw.githubusercontent.com/google/google-authenticator-libpam/master/README.md>
- <https://raw.githubusercontent.com/google/google-authenticator-libpam/master/man/pam_google_authenticator.8.md>
- <https://sources.debian.org/src/google-authenticator/>
- <https://www.rfc-editor.org/rfc/rfc4226>
- <https://www.rfc-editor.org/rfc/rfc6238>


## セキュリティノート

narrow executable package without higher-risk signals.

- **Geiger リスク:** グリーン / 低
- narrow executable package without higher-risk signals


## Configuration and credential file locations

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 files

- Unix: ~/.google_authenticator
## 他のパッケージマネージャ記録

- zypper - google-authenticator-libpam - 1.10-3.5: normalized package name match | openSUSE Tumbleweed package metadata: google-authenticator-libpam from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Google Authenticator PAM module | https://github.com/google/google-authenticator-libpam
- Debian apt - libpam-google-authenticator - 20191231-2.1: installed executable or alias match | Debian stable package indexes: libpam-google-authenticator from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | Two-step verification | https://github.com/google/google-authenticator-libpam
- Nix - google-authenticator: installed executable or alias match | nixpkgs package indexes: pkgs/by-name/go/google-authenticator/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- Ubuntu apt - libpam-google-authenticator - 20191231-2build1: installed executable or alias match | Ubuntu 24.04 LTS package indexes: libpam-google-authenticator from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | Two-step verification | https://github.com/google/google-authenticator/
- apk - google-authenticator - 1.11-r0: installed executable or alias match | Alpine Linux edge package indexes: google-authenticator from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Google Authenticator PAM module | https://github.com/google/google-authenticator-libpam
- apk - google-authenticator-doc - 1.11-r0: installed executable or alias match | Alpine Linux edge package indexes: google-authenticator-doc from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Google Authenticator PAM module (documentation) | https://github.com/google/google-authenticator-libpam
- dnf - google-authenticator - 1.11-5.fc45: installed executable or alias match | Fedora Rawhide package metadata: google-authenticator from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst | One-time pass-code support using open standards | https://github.com/google/google-authenticator-libpam/


## Combined YAML source

View the package source record on GitHub. [combined/google-authenticator-libpam.yml](https://github.com/mxcl/pkgdb/blob/main/combined/google-authenticator-libpam.yml)


## ソース

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph
