SQ(1)

🎀 sq-key-approvals — the certification-approvals vibe 🎀

okay so hi bestie 💖 this is the SQ(1) manual page, straight off the User Commands shelf, and it's literally all about sq-key-approvals. Yes the title is SQ(1), and yes that one's short for the whole sq fam — we'll get to them in SEE ALSO, don't worry 🫶

---

✨ NAME ✨

sq-key-approvals — Manages certification approvals 💅

---

🌸 SYNOPSIS 🌸

sq key approvals list [OPTIONS]
sq key approvals update [OPTIONS]

two subcommands, two moods, both iconic 👑

---

🦋 DESCRIPTION 🦋

okay so. sq-key-approvals manages certification approvals. that's the whole job, periodt.

here's the tea ☕ : key holders are allowed to approve of third-party certifications that are attached to their certificate. and this subcommand is the one that manages all those approvals. main character energy fr fr.

now, the why — because this part actually matters, no cap:

to prevent certificate flooding attacks 😭, modern key servers do not let third-party certifications just rain down on a certificate uncontrolled. instead, to give the key holder control over what info gets distributed alongside their certificate, those key servers only hand out third-party certifications that the key holder has explicitly approved.

so like… no approval, no distribution. simple as that ✨

---

🐛 SUBCOMMANDS 🐛

---

sq key approvals list

Lists third-party certifications and their approval status. 📋

and the details, because the details are the whole point:

to prevent certificate flooding attacks 😭, modern key servers do not distribute third-party certifications on a certificate in an uncontrolled way. to let the key holder control what information is distributed with their certificate, these key servers only distribute third-party certifications that the key holder has explicitly approved.

---

sq key approvals update

Approves of third-party certifications allowing for their distribution. ✅

same caveat bestie, here it is again:

to prevent certificate flooding attacks 😭, modern key servers prevent the uncontrolled distribution of third-party certifications on certificates. so that the key holder gets to control what info ships with their certificate, these key servers only distribute third-party certifications that the key holder has explicitly approved.

a couple of very important deets 👇

• by default, all user IDs are considered — but if you pass at least one --name, --email, or --userid argument, then only the matching user IDs get considered. like, that's the filter, that's the vibe.
• and AFTER the approvals have been changed, the certificate has to be distributed, e.g. by uploading it to a key server. approving is not the same as publishing, so don't forget the second step 🙈

---

🔥 EXAMPLES 🔥

manifesting correct syntax for you 🕯️✨

---

sq key approvals list

Lists the approved certifications on all the user IDs.

sq key approvals list \
      --cert=EB28F26E2739A4870ECC47726F0073F60FD0CBF0

Lists the unapproved certifications on all the user IDs.

sq key approvals list --pending \
      --cert=EB28F26E2739A4870ECC47726F0073F60FD0CBF0

Lists all unapproved certifications on a given user ID.

sq key approvals list --pending --email=alice@example.org \
      --cert=EB28F26E2739A4870ECC47726F0073F60FD0CBF0

---

sq key approvals update

Approve of all of the certifications on all of Alice's user IDs.

sq key approvals update --add-all \
      --cert=EB28F26E2739A4870ECC47726F0073F60FD0CBF0

Approve of all of the certifications on all of Alice's user IDs made by Bob, discarding all prior approvals first.

sq key approvals update --remove-all \
      --add-by=511257EBBF077B7AEDAE5D093F68CB84CE537C9A \
      --cert=EB28F26E2739A4870ECC47726F0073F60FD0CBF0

Approve of all of the certifications on a specific user ID by certifiers that can be authenticated, discarding all prior approvals first.

sq key approvals update --remove-all --add-authenticated \
      --cert=EB28F26E2739A4870ECC47726F0073F60FD0CBF0 \
      --userid="Alice <alice@example.org>"

Remove the approval of Bob's certification on all of Alice's user IDs.

sq key approvals update \
      --remove-by=511257EBBF077B7AEDAE5D093F68CB84CE537C9A \
      --cert=EB28F26E2739A4870ECC47726F0073F60FD0CBF0

---

👑 SEE ALSO 👑

go read these next, bestie, they're all part of the same friend group:

• sq(1)
• sq-key(1)
• sq-key-approvals-list(1)
• sq-key-approvals-update(1)

and for the full documentation (the deluxe version, the director's cut 🌈) see https://book.sequoia-pgp.org/.

---

💜 VERSION 💜

1.5.0 — that's the one, the current era ✨

---

ok that's the whole page bestie, you ate it 💅 go approve something responsibly

Sequoia PGP · version 1.5.0 · mwah, tysm for reading, ily 🫶🎀🦋💖