SQ(1)

πŸ’– SQ-CERT-EXPORT β€” the girlies' guide πŸ’–

okay so bestie, welcome to sq-cert-export, which lives inside the sq(1) manual (the User Commands girlies ✨). This is the little helper that pulls certificates out of your local certificate store. Grab a strawberry πŸ“, we're doing this.


✨ NAME ✨

sq-cert-export β€” export certificates from the local certificate store. that's it, that's the whole job, and she does it flawlessly πŸ’…


🌸 SYNOPSIS 🌸

sq cert export [OPTIONS]

πŸ¦‹ DESCRIPTION πŸ¦‹

So like, this exports certificates from the local certificate store. simple queen behavior.

If you give her multiple predicates, she returns a certificate if at least one of them matches. OR vibes only, no cap.

⚠️ Big one: this does not check the authenticity of the certificates in any way. Before you use them, pls pls pls validate and authenticate them. don't skip this step bestie, i'm begging 😭

When you're matching on subkeys or User IDs, the component has to have a valid self signature according to the policy. no valid self sig, no match, that's the rule πŸŽ€

And here's the ✨iconic✨ little twist: it fails if search criteria are specified and none of them matches any certificates. Note the lore here β€” this means if the certificate store is empty and you specified no search criteria, it'll return success. empty store + no filters = she's thriving, success, we love a low-effort win πŸ’€


πŸ”₯ OPTIONS πŸ”₯

Subcommand options πŸ‘‘

  • --all β€” export all the certificates. the whole collection. main character energy, no filter 🌈
  • --cert=FINGERPRINT|KEYID β€” use certificates with the fingerprint or key ID you name. FINGERPRINT or KEYID, your call πŸ’œ
  • --cert-domain=DOMAIN β€” use certificates where a user ID includes an email address for the domain you specify
  • --cert-email=EMAIL β€” use certificates where a user ID includes that exact email address you typed
  • --cert-grep=PATTERN β€” use certificates with a user ID that matches the pattern, and it's case insensitively matched (so chill about capitalization, she's not gonna be picky) 🫢
  • --cert-userid=USERID β€” use certificates with the specified user ID
  • --local β€” export local (non-exportable) signatures πŸ”

By default, non-exportable signatures are not emitted when exporting certificates, certificate components that are only bound by non-exportable signatures are not emitted, and certificates consisting of only non-exportable components are not emitted. so like, the default is very strict, she's gatekeeping a lil bit.

This flag flips that: it enables exporting of non-exportable signatures, components, and certs. This is useful for synchronization between your own devices, for example. (iconic for the multi-device girlies ✨)

  • --output=FILE β€” write to FILE, or to stdout if you omit it

[default: -]

Global options 🌍

See sq(1) for a description of the global options. (she's got a whole extended universe, go read her page)


πŸŽ€ EXAMPLES πŸŽ€

Export certificates with a User ID containing the email address:

sq cert export --cert-email=alice@example.org

Export certificates that contain a User ID with either (not both!) email address:

sq cert export --cert-email=alice@example.org \
       --cert-email=bob@example.org

Export all certificates:

sq cert export --all
πŸ’€ not the "either, not both" β€” yes bestie, two --cert-email flags means OR, not AND. she said at least one, remember? don't come for me, that's just the lore.

πŸ‘€ SEE ALSO πŸ‘€

For the full documentation see <https://book.sequoia-pgp.org/>. it's giving study material, but like, the good kind πŸ“šπŸ’–


⭐ VERSION ⭐

1.5.0


okay that's the whole page bestie, you ate that πŸ«ΆπŸ’… the version is 1.5.0, it's from the Sequoia PGP girlies, and it's dated 1.5.0 too (yes, same number, she said consistency ✨). now go export some certs responsibly, validate them like i told you, and have the best day fr fr πŸŒΈπŸ§šπŸ’œ

πŸ“¦ where this page comes from