SQ(1)
π SQ(1) β sq-key-approvals-update π
okay bestie, so this manual page is for sq-key-approvals-update β and before you ask, yes, the manual is called SQ and the section is 1. The command lives under sq key approvals update. Let's get into it β¨
π NAME π
sq-key-approvals-update β literally just says yes to third-party certifications so they can actually be distributed. giving approval vibes fr fr π
π¦ SYNOPSIS π¦
sq key approvals update [OPTIONS]
πΈ DESCRIPTION πΈ
So here's the tea: this command approves of third-party certifications allowing for their distribution. That's the whole job. π
Why does anybody care? To prevent certificate flooding attacks, modern key servers don't just let third-party certifications on certificates float around uncontrolled. And to let the key holder control what info gets distributed alongside their certificate, these key servers only distribute third-party certifications that the key holder has explicitly approved. Like, consent only, no surprises. π«Ά
By default, all user IDs are considered. But β and this is the plot twist β if you give at least one --name, --email, or --userid argument, only the matching user IDs get considered. narrow it down babes β¨
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 finish line, it's the glow-up and then you have to go out. π
β¨ OPTIONS β¨
π Subcommand options
--add-allβ Approve of all pending certifications. everything, all of it, no notes π--add-authenticatedβ Approve of all certifications by authenticated certifiers. For all pending approvals, try to authenticate any user ID on the certifier, and if any can be authenticated, approve of the certification. yes bestie, we're checking IDs at the door π₯--add-by=FINGERPRINT|KEYIDβ Approve of all certifications by this certifier.--cert=FINGERPRINT|KEYIDβ List the approvals on the certificate with the specified fingerprint or key ID.--cert-email=EMAILβ List the approvals on the certificate where a user ID includes the specified email address.--cert-file=PATHβ List the approvals on the certificate read fromPATH.--cert-userid=USERIDβ List the approvals on the certificate with the specified user ID.--email=EMAILβ Use the self-signed user ID with the specified email address.--output=FILEβ Write to the specifiedFILE. If not specified, and the certificate was read from the certificate store, imports the modified certificate into the cert store. If not specified, and the certificate was read from a file, writes the modified certificate tostdout. iykyk π--remove-allβ Remove all prior approvals. By default, this command adds to the set of already approved certifications. If this flag is given, the existing approvals are disregarded, and only the newly selected certifications are approved, if any. clean slate energy, periodt π--remove-by=FINGERPRINT|KEYIDβ Remove all prior approvals of certifications by this certifier.--userid=USERIDβ Use the specified self-signed user ID. The specified user ID must be self signed. no exceptions bestie π¨
πΊ Global options
See sq(1) for a description of the global options. (yes, we're pointing you at the main character's page π)
π« EXAMPLES π«
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 π
sq(1), sq-key(1), sq-key-approvals(1).
For the full documentation see <https://book.sequoia-pgp.org/>. go read it, it's giving academic but make it cute πβ¨
β VERSION β
1.5.0
and that's the whole page bestie!! this one came from Sequoia PGP, version 1.5.0, dated 1.5.0 β shoutout to them, we love a well-documented tool π mwah, see you in the next manpage π«Άβ¨
π¦ where this page comes from
- fedora 43: sequoia-sq 1.5.0-1.fc43 Β· LGPL-2.0-or-later AND Apache-2.0 AND BSL-1.0 AND BSD-3-Clause AND MIT AND MPL-2.0 AND Unicode-3.0 AND Unicode-DFS-2016 AND Zlib AND bzip2-1.0.6 AND (0BSD OR MIT OR Apache-2.0) AND (Apache-2.0 OR BSL-1.0) AND (Apache-2.0 OR MIT) AND (Apache-2.0 WITH LLVM-exception OR Apache-2.0 OR MIT) AND (BSD-2-Clause OR Apache-2.0 OR MIT) AND (MIT OR Apache-2.0 OR Zlib) AND (Unlicense OR MIT)
- fedora 44: sequoia-sq 1.5.0-1.fc44 Β· LGPL-2.0-or-later AND Apache-2.0 AND BSL-1.0 AND BSD-3-Clause AND MIT AND MPL-2.0 AND Unicode-3.0 AND Unicode-DFS-2016 AND Zlib AND bzip2-1.0.6 AND (0BSD OR MIT OR Apache-2.0) AND (Apache-2.0 OR BSL-1.0) AND (Apache-2.0 OR MIT) AND (Apache-2.0 WITH LLVM-exception OR Apache-2.0 OR MIT) AND (BSD-2-Clause OR Apache-2.0 OR MIT) AND (MIT OR Apache-2.0 OR Zlib) AND (Unlicense OR MIT)
- nixpkgs unstable: sequoia-sq 1.5.0
- opensuse-leap 16.0: sequoia-sq 1.5.0-bp160.1.1 Β· LGPL-2.0-or-later
- opensuse-leap 16.0: sequoia-sq 1.5.0-bp160.1.1 Β· LGPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms