SQ(1)

πŸ’– SQ(1) β€” the manual, but make it cute πŸ’–

okay bestie, listen up: this is the man page for sq-pki-vouch-replay, which lives inside the sq command family. `certificate glow-ups, let's gooo ✨


πŸŽ€ NAME

sq-pki-vouch-replay β€” Replays vouches πŸ’…


🌸 SYNOPSIS

sq pki vouch replay [OPTIONS]

that's it. that's the whole vibe. ✨


πŸ¦‹ DESCRIPTION

Replays vouches. (yes, literally, that's what it does, and honestly? iconic.)

So here's the tea β˜•: this command replays the vouches made by one certificate using another certificate. When is that useful, you ask? It's primarily useful when you replace a certificate, and you want the new certificate to have made the same certifications as you made with the old certificate. Basically your new cert inherits your old cert's whole friend list. 🫢

Because certifications are associated with the certificated certificate, and not the certifier's certificate, this may not replay all of the certifications that the source ever made. lowkey important β€” don't come for me if some stuff doesn't show up, the data model just do be like that 😭

This command only copies the active certification for a given user ID and certificate. Bestie, "only" is doing a LOT of heavy lifting there, so let's get specific: this includes both exportable certifications (vouches) as well as non-exportable certifications (links). It excludes expired certifications. It also doesn't replay certifications made on invalid, expired or revoked certificates, or revoked user IDs. nope, expired and revoked stuff is not invited to the party 🚫

This command replays all of the certifications parameters including any expiration time, but the creation time is set to the current time. so the expiration rides along, but the creation timestamp is like "it's giving… now." πŸ•

Stable since 1.2.0. πŸ‘‘


✨ OPTIONS ✨

πŸ’œ Subcommand options

  • --allow-dissimilar-userids β€” Don't check that the source and target share a self-signed user ID.

Normally, this command checks that the source and target certificates have a user ID in common. This flag skips that check. (it's the "we're not technically the same person but go off" flag πŸ™ˆ)

  • --output=FILE β€” Write to FILE or stdout if omitted. standard behavior, she's flexible like that πŸ’…
  • --source=FINGERPRINT|KEYID β€” Use certificates with the specified fingerprint or key ID. ✨
  • --source-email=EMAIL β€” Use certificates where a user ID includes the specified email address. πŸ“§
  • --source-file=PATH β€” Read certificates from PATH. πŸ“‚
  • --source-userid=USERID β€” Use certificates with the specified user ID. πŸͺͺ
  • --target=FINGERPRINT|KEYID β€” Use certificates with the specified fingerprint or key ID. ✨
  • --target-email=EMAIL β€” Use certificates where a user ID includes the specified email address. πŸ“§
  • --target-file=PATH β€” Read certificates from PATH. πŸ“‚
  • --target-userid=USERID β€” Use certificates with the specified user ID. πŸͺͺ

so yeah, it's giving very much a matched set: --source-something tells her who you were, --target-something tells her who you are now. 🌈

🌟 Global options

See sq(1) for a description of the global options. she's not repeating herself, go read the main page bestie 🫢


πŸ”₯ EXAMPLES

Alice generates a new certificate, and replays the certifications she made with the old certificate using the new one. main character behavior, honestly πŸ‘‘

sq pki vouch replay \
       --source=EB28F26E2739A4870ECC47726F0073F60FD0CBF0 \
       --target=C5999E8191BF7B503653BE958B1F7910D01F86E5

not me copying those fingerprints exactly character for character, because I do not play with hex πŸ’€


🌈 SEE ALSO

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


⭐ VERSION

1.5.0


okay that's the whole page, you ate that fr fr πŸ’– and one last thing before you go β€” this cutie is brought to you by Sequoia PGP, running version 1.5.0, so shoutout to the whole squad for making it happen. periodt. πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from