SQ(1)

πŸ’– SQ(1) β€” the sq network keyserver era πŸ’–

okay bestie, sit down, hydrate, and let me tell you about sq-network-keyserver β€” she retrieves and publishes certificates via key servers, and honestly? she ate. ✨


🌈 NAME 🌈

sq-network-keyserver β€” Retrieve and publishes certificates via key servers πŸ¦‹


✨ SYNOPSIS ✨

sq network keyserver search [OPTIONS] QUERY
sq network keyserver publish [OPTIONS]

πŸ’… DESCRIPTION πŸ’…

Retrieve and publishes certificates via key servers. no cap, that's the whole vibe. πŸŽ€

The OpenPGP HTTP Keyserver Protocol (HKP) is a method for publishing and retrieving certificates from key servers. that's it, that's the protocol β€” HKP is the moment for getting certs in and out of key servers. πŸ‘‘


🫢 SUBCOMMANDS 🫢

Retrieve certificates from key servers. it's giving "go get her."

By default, any returned certificates are stored in the local certificate store. This can be overridden by using --output option. so like, default behavior = they land in your local cert store, unless you say otherwise with --output. πŸ’Ύ

When a certificate is retrieved from a verifying key server (currently, this is limited to a list of known servers: hkps://keys.openpgp.org, hkps://keys.mailvelope.com, and hkps://mail-api.proton.me), and imported into the local certificate store, the User IDs are also certificated with a local server-specific key. πŸ—οΈ That proxy certificate is in turn certified as a minimally trusted CA (trust amount: 1 of 120) by the local trust root. lowkey a chain reaction, highkey on purpose. How much a proxy key server CA is trusted can be tuned using sq pki link add or sq pki link retract in the usual way. tune it, bestie, it's yours to tune. πŸŽ›οΈ

πŸ“€ sq network keyserver publish

Publish certificates on key servers. put her out there, main character behavior.

Sends certificates to the configured key servers for publication. By default, the certificates are sent to hkps://keys.openpgp.org, hkps://mail-api.proton.me, hkps://keys.mailvelope.com, hkps://keyserver.ubuntu.com, and hkps://sks.pod01.fleetstreetops.com. This can be tweaked using --servers. that's five servers out of the box, and you can swap the lineup with --servers. ⭐


🌸 EXAMPLES 🌸

πŸ” sq network keyserver search

Retrieve Alice's certificate from the default keyservers.

sq network keyserver search alice@example.org

Retrieve Alice's certificate addressed by fingerprint from the default keyservers.

sq network keyserver search \
       EB28F26E2739A4870ECC47726F0073F60FD0CBF0

Retrieve Alice's certificate from a non-default keyserver.

sq network keyserver search --server=hkps://keys.example.org \
       alice@example.org

Retrieve updates for all known certificates from the default keyservers.

sq network keyserver search --all

πŸ“€ sq network keyserver publish

Publish Alice's certificate on the default keyservers.

sq network keyserver publish --cert-email=alice@example.org

πŸ‘€ SEE ALSO πŸ‘€

For the full documentation see <https://book.sequoia-pgp.org/>. go read it, iykyk πŸ“š


πŸ’œ VERSION πŸ’œ

1.5.0


and that's the whole page, bestie β€” written by the Sequoia PGP girlies, Sequoia PGP, version 1.5.0 πŸ’– no notes, periodt. now go fetch some certs. πŸ¦‹βœ¨πŸŽ€

πŸ“¦ where this page comes from