APPLYGNUPGDEFAULTS(8)

✨ NAME ✨ β€” applygnupgdefaults(8) from GNU Privacy Guard 2.4 ✨

applygnupgdefaults β€” run gpgconf --apply-defaults for all users. That's literally the whole name bestie πŸ’…


🌸 SYNOPSIS 🌸

applygnupgdefaults

No flags, no arguments, just the command. Iconic ✨


πŸ’… DESCRIPTION πŸ’…

Okay so real talk: this is a legacy script 🫢. Modern application should use the per component global configuration files under /etc/gnupg/ instead β€” that's the current main-character path, iykyk.

This script is a wrapper around gpgconf to run it with the command --apply-defaults for all real users with an existing GnuPG home directory. It's giving "batch update the whole group chat" energy πŸ‘‘βœ¨

Admins might want to use this script to update the GnuPG configuration files for all users after /etc/gnupg/gpgconf.conf has been changed. This allows enforcing certain policies for all users. Slay for policy consistency πŸ’–

But no cap: this is not a bulletproof way to force a user to use certain options. A user may always directly edit the configuration files and bypass gpgconf. So it's a vibe check, not a jail πŸ”“πŸ’€

applygnupgdefaults is invoked by root as:

applygnupgdefaults

Root runs it, and the script does its gpgconf --apply-defaults thing for all the real users with an existing GnuPG home directory β€” that's the tea β˜•βœ¨


πŸ’– That's the whole manual! Source/version check: GnuPG 2.4.9, dated 2025-02-19, and this is the applygnupgdefaults(8) page β€” bye bestie, go update those defaults responsibly! πŸ«ΆπŸ’…

πŸ“¦ where this page comes from