SQ(1)

πŸ’– SQ(1) β€” the squad's fave manual πŸ’–

okay bestie, buckle up, this is sq(1) energy β€” a User Commands page, and today's main character is sq-pki-vouch-list. yes the page header says SQ(1) but the tea is all about listing certifications. let's go πŸ¦‹


✨ NAME ✨

sq-pki-vouch-list β€” List certifications


🌸 SYNOPSIS 🌸

sq pki vouch list [OPTIONS]

πŸ‘‘ DESCRIPTION πŸ‘‘

So. We're listing certifications. That's the whole vibe. πŸ’…

Here's the lil logic of it, and this part matters:

  • If the certifier argument is provided, then certifications made by the specified certificate are shown.
  • If the certificate argument is provided, then certifications of the specified certificate are shown.
  • If both are provided, then certifications of the specified certificate made by the specified certifier are shown.

Read this one twice, bestie: this command lists all of certifications, not just the active certification. no filtering by vibe check, we're showing the whole album πŸ“Έ

And here's the part that's giving "the tea is incomplete, ngl": because certifications are associated with the certificated certificate and not the certifier's certificate, this list is likely incomplete. 😭 fr fr. it's not a bug, it's just how the data sits.

Stable since 1.2.0. β€” she's been iconic for a minute now πŸ’–


πŸŽ€ OPTIONS πŸŽ€

Subcommand options 🌈

  • --cert=FINGERPRINT|KEYID β€” use certificates with the specified fingerprint or key ID
  • --cert-email=EMAIL β€” use certificates where a user ID includes the specified email address
  • --cert-file=PATH β€” read certificates from PATH
  • --cert-userid=USERID β€” use certificates with the specified user ID
  • --certifier=FINGERPRINT|KEYID β€” use certificates with the specified fingerprint or key ID
  • --certifier-email=EMAIL β€” use certificates where a user ID includes the specified email address
  • --certifier-file=PATH β€” read certificates from PATH
  • --certifier-self β€” create the certification using your default certification key
    • this uses the certificates set in the configuration file under pki.vouch.certifier-self as certification key
    • currently, there is no default certification key. 🫠 so yeah, don't count on that one yet
  • --certifier-special=SPECIAL β€” use certificates identified by the special name
    • possible values: public-directories, keys.openpgp.org, keys.mailvelope.com, proton.me, wkd, dane, autocrypt, web β€” the squad of special names, say hi to all eight 🫢
  • --certifier-userid=USERID β€” use certificates with the specified user ID

Global options 🌍

See sq(1) for a description of the global options. iykyk, the global options live in their own house.


⭐ EXAMPLES ⭐

List certifications made by Alice. (she ate, obviously) πŸ’…

sq pki vouch list \
       --certifier=EB28F26E2739A4870ECC47726F0073F60FD0CBF0

List certifications made by Alice for Bob's certificate. (the collab we've all been waiting for 🀝)

sq pki vouch list \
       --certifier=EB28F26E2739A4870ECC47726F0073F60FD0CBF0 \
       --cert=511257EBBF077B7AEDAE5D093F68CB84CE537C9A

πŸ¦‹ SEE ALSO πŸ¦‹

For the full documentation see <https://book.sequoia-pgp.org/>.


🧚 VERSION 🧚

1.5.0


okay that's the whole page, no notes, you understood it perfectly bestie 🌸 this has been sq(1) β€” Sequoia PGP, version 1.5.0, and yeah it's literally 1.5.0 again in the footer bc the squad keeps it consistent ✨ periodt πŸ’œ

πŸ“¦ where this page comes from