PAM-AUTH-UPDATE(8)

๐Ÿ“ฆ
version 1.7.0 ยท 2 versions
  • 1.7.0 ยท debian bookworm, debian trixie, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 1.4.0 ยท ubuntu jammy
, in debian bookworm, debian trixie, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

โœจ PAM-AUTH-UPDATE(8) โ€” NAME โœจ

okay so bestie, this is the manual for pam-auth-update, the tool that lets you manage PAM configuration using packaged profiles ๐Ÿ’…๐Ÿ”

๐ŸŽ€ NAME

pam-auth-update - manage PAM configuration using packaged profiles ๐ŸŒธ

๐Ÿฆ‹ SYNOPSIS

pam-auth-update [--package [--remove profile [profile...]]]  [--force]
[--enable profile [profile...]]  [--disable profile [profile...]]

๐Ÿ’– DESCRIPTION

okay so pam-auth-update is a utility that lets you configure the central authentication policy for the system using pre-defined profiles that come from PAM module packages. it's giving organized ๐Ÿงš

profiles shipped in the /usr/share/pam-configs/ directory are the ones that specify the modules (plus their options) to enable, the preferred ordering compared to other profiles, and whether a profile should be enabled by default. so iconic โœจ

packages that provide PAM modules register their profiles at install time by calling pam-auth-update --package. picking profiles is done through the standard debconf interface. the profile selection question gets asked at medium'</lavender> priority when packages are added or removed, so no user interaction is required by default ๐Ÿ™ˆ users can also invoke pam-auth-update` directly to change their authentication configuration whenever they want ๐Ÿ’œ

the script makes every effort to respect local changes to /etc/pam.d/common-*. local modifications to the list of module options will be preserved, BUT additions of modules within the managed portion of the stack will make pam-auth-update treat the config files as locally modified, and it won't make further changes to them unless you give it the --force option ๐Ÿ˜ญ

if you tell pam-auth-update to override local configuration changes, the locally-modified files get saved in /etc/pam.d/ with a suffix of .pam-old. save your stuff, bestie ๐Ÿซถ

๐ŸŒˆ OPTIONS

  • --package โ€” this tells pam-auth-update that the caller is a package maintainer script. it lowers the priority of debconf questions to `medium' so the user doesn't get prompted by default ๐Ÿ“
  • --disable profile [profile...] โ€” disables the specified profiles in the system configuration. system admin scripts can use this to switch profiles off ๐ŸŒ™
  • --enable profile [profile...] โ€” enables the specified profiles in the system configuration. this is how you turn on profiles that aren't on by default โญ
  • --remove profile [profile...] โ€” removes the specified profiles from the system configuration. the vibe: always run pam-auth-update --remove BEFORE the modules they reference get deleted from disk, so PAM stays consistent and usable the whole time during package upgrades or removals ๐Ÿ”ฅ
  • --force โ€” overwrites the current PAM configuration without prompting. โš ๏ธ this one must NOT be used by package maintainer scripts; it's for administrators only ๐Ÿ’€

๐Ÿ“‚ FILES

  • /etc/pam.d/common-* โ€” global PAM configuration, affecting all installed services ๐ŸŽ€
  • /usr/share/pam-configs/ โ€” package-supplied authentication profiles ๐Ÿงš

๐Ÿ‘‘ AUTHOR

Steve Langasek <steve.langasek@canonical.com> ๐Ÿ’œ

Copyright (C) 2008 Canonical Ltd. ๐Ÿฆ‹

๐Ÿ”— SEE ALSO

PAM(7), pam.d(5), debconf(7) โœจ


that's the whole tea, bestie ๐Ÿซถ this page was from Debian, version 08/23/2008, and it's the manual for PAM-AUTH-UPDATE(8). periodt ๐Ÿ’…๐Ÿ’–

๐Ÿ“ฆ where this page comes from