PIUS-KEYRING-MGR(1)

πŸ’– pius-keyring-mgr β€” the NAME bit πŸ’–

okay so bestie, meet pius-keyring-mgr β€” the PIUS (PGP Individual UID Signer) Keyring Manager πŸŽ€. That's the whole name, no cap. It's a General Commands Manual page, section 1, and it's here to help you wrangle keyrings like the main character you are πŸ‘‘.


πŸ¦‹ SYNOPSIS πŸ¦‹

pius-keyring-mgr <mode> [options]

✨ DESCRIPTION ✨

so pius-keyring-mgr has several modes for managing keyrings πŸ’…. It was originally designed for signing parties, but honestly? It works on any PGP keyring. It's giving versatile.

The one rule: the mode must be the first argument β€” like, first, bestie, before anything else β€” and then the options come after, as explained below ⬇️.


πŸ’… OPTIONS πŸ’…

  • -d, --debug β€” turns on debugging output πŸ” so you can see what's actually going on.
  • -g PATH, --gpg-path=PATH β€” where your gpg binary lives 🧚. [default: /usr/bin/gpg2]
  • -r KEYRING, --keyring=KEYRING β€” use this keyring, this one right here πŸ’–.
  • -v, --verbose β€” prints summaries πŸ“. Yes, it's chatty, we love that for it.

🌈 MODES 🌈

πŸ› οΈ build

build mode is the one you'll use pretty much all the time. It can parse a CSV file πŸ“„, automatically go looking for keys πŸ”Ž, and email anyone whose key wasn't found πŸ“§. It can also import keys from an mbox file. The options are:

  • -b MBOX-FILE, --mbox-file=MBOX-FILE β€” parses MBOX-FILE and checks every single message for PGP fingerprints or ascii-armored keys πŸ”‘. It decodes messages as needed.
  • -c CSV-FILE, --csv-file=CSV-FILE β€” parses MBOX-FILE and imports keys. (yes bestie, it really says MBOX-FILE right there πŸ™ˆ β€” I'm just the messenger, I don't make the rules.) You will almost certainly also want -D, -E, -F and -N πŸ’….
  • -D DELIMITER, --delimiter=DELIMITER β€” the field delimiter to use when parsing CSV. Only meaningful with -c. [default: ',']
  • -E EMAIL-COLUMN, --email-field=EMAIL-COLUMN β€” which column number holds the email address in the CSV file πŸ“§. Only meaningful with -c. [default: 3]
  • -F FINGERPRINT-COLUMN, --fp-field=FINGERPRINT-COLUMN β€” which column number holds the GPG fingerprint in the CSV file πŸ”‘. Only meaningful with -c. [default: 4]
  • -m FROM-EMAIL, --mail=FROM-EMAIL β€” emails the people whose keys were not located, using FROM-EMAIL as the sender πŸ“¨.
  • -M FILE, --mail-text=FILE β€” uses the text in FILE as the body of the email instead of the default text ✍️. Wanna see the default text? Use --print-default-email. Requires -m.
  • -N NAME-COLUMN, --name-field=NAME-COLUMN β€” which column number holds the name in the CSV file 🏷️. Only meaningful with -c. [default: 2]
  • -n TO-EMAIL, --override-email=TO-EMAIL β€” instead of sending to the actual user, send to this address πŸ‘€. Mostly useful for debugging.
  • -p PARTY-NAME, --party=PARTY-NAME β€” the name of the party πŸŽ‰. It gets printed in the email that goes out. Only useful with -m.
  • -s KEY-SERVER, --keyservers=KEY-SERVER β€” try this keyserver 🌐. Specify it once for each server you want (-s foo -s bar). [default: pool.sks-keyservers.net, pgp.mit.edu, keys.gnupg.net]
  • -t TEMP-DIR, --tmp-dir=TEMP-DIR β€” the directory to dump temporary stuff in πŸ“. [default: /tmp/pius_keyring_mgr_tmp]
  • -T, --print-default-email β€” prints the default email πŸ“¬.
  • --ignore-emails=IGNORE-EMAILS β€” a comma-separated list of emails to ignore (no spaces!) 🚫.
  • --ignore-fingerprints=IGNORE-FINGERPRINTS β€” a comma-separated list of PGP fingerprints to ignore (again, no spaces) πŸ™….

βœ‚οΈ prune

prune mode opens a keyring and, for each key, asks you whether to remove it πŸ—‘οΈ. Super useful after a party to trim out the people who didn't show up, before you hand the keyring out to the people who did ✨. There are no options. That's it. Simple. Iconic.

πŸ§ͺ raw

raw mode passes options directly to gpg 🫢. Great for adding keys by hand. Your options get added to the ones needed to safely work on the party keyring β€” and nope, it does not load your personal keyring 🚫. Your options must be passed after -- so that pius-keyring-manager doesn't try to interpret them as its own πŸ™ˆ.


🌸 EXAMPLES 🌸

Scan a CSV file and an MBOX for emails, then write to anyone whose key wasn't found, using you@company.com as the sender:

/usr/bin/pius-keyring-mgr build --csv-file /tmp/report --mbox-file /tmp/mbox --mail you@company.com

Download a key and add it to the party keyring:

pius-keyring-mgr raw -r path/to/keyring.gpg -- --recv-key <keyid>

πŸ‘‘ AUTHOR πŸ‘‘

PIUS was written by Phil Dibowitz <phil@ipom.com> πŸ’œ.

This manual page was written by Felix Lechner <felix.lechner@gmail.com> for the Debian project, but may be used by others 🫢. (Sharing is caring, bestie.)


okay that's the whole page!! πŸŽ€βœ¨ this was PIUS-KEYRING-MGR(1) from the General Commands Manual, and the page itself is dated DECEMBER 2016 πŸ“…. go forth and manage those keyrings, you absolute legend πŸ‘‘πŸ’– periodt.