SQ(1)

💖 SQ(1) — the sq manual, but make it cute 💖

okay bestie, so this page is from the sq manual (User Commands, in case you were wondering) and it's all about one lil subcommand, sq-key-userid-add. grab a strawberry 🍓 and let's go.

---

✨ NAME ✨

sq-key-userid-add — add a user ID 💅

---

🦋 SYNOPSIS 🦋

sq key userid add [OPTIONS]

---

🌸 DESCRIPTION 🌸

Add a user ID. that's it, that's the whole vibe. adding identity info to a key, iconic behavior.

a user ID can have a name, like Juliet, or an email address, like <juliet@example.org>. bestie, historical tea ☕: back in the day a name and an email address were usually smooshed into a single user ID, like Juliet <juliet@example.org>. but here's the thing — user IDs that mix different kinds of info (name AND email, together) are lowkey harder to reason about 🧠😵, so nowadays the preferred move is to use distinct user IDs for the name and for the email address. separate. clean. slay.

also important: sq key userid add respects the reference time set by the top-level --time argument ⏰. it sets the creation time of the user ID's binding signature to whatever time you specified. fr fr.

---

✨ OPTIONS ✨

🎀 Subcommand options

• --allow-non-canonical-userids — don't reject user IDs that aren't in canonical form. ico— canonical user IDs are of the form Name (Comment) <localpart@example.org>. so if it's not shaped like that, this flag is your "it's fine, let it in" pass 🫶.
• --cert=FINGERPRINT|KEYID — add the user ID to the key with the specified fingerprint or key ID 🔑.
• --cert-email=EMAIL — add the user ID to the key where a user ID includes the specified email address 📧.
• --cert-file=PATH — add the user ID to the key read from PATH 📂.
• --cert-userid=USERID — add the user ID to the key with the specified user ID 🏷️.
• --email=ADDRESS — add an email address as user ID to the key ✉️.
• --name=NAME — add a name as user ID to the key 🪪.
• --output=FILE — write to the specified FILE 📝.
  • if you don't specify it, and the certificate was read from the certificate store, it imports the modified certificate into the cert store.
  • if you don't specify it, and the certificate was read from a file, it writes the modified certificate to stdout. (so like, careful where that goes 👀)
• --userid=USERID — add a user ID to the key.
  • this user ID can combine name and email address, can optionally contain a comment, or even be free-form if --allow-non-canonical-userids is given. but bestie, remember — user IDs that include different information such as name and email address are more difficult to reason about, so using distinct user IDs for name and email address is preferred nowadays.
  • in doubt, prefer --name and --email. like genuinely, that's the move 💯.

🌈 Global options

• see sq(1) for a description of the global options. yes girl, go read the parent page, it's giving main character energy 👑

---

💫 EXAMPLES 💫

# Add a new user ID to Alice's key.

sq key userid add --cert \
       EB28F26E2739A4870ECC47726F0073F60FD0CBF0 --name Alice \
       --email alice@work.example.com

---

👀 SEE ALSO 👀

• sq(1), sq-key(1), sq-key-userid(1).
• for the full documentation see <https://book.sequoia-pgp.org/>.

---

🏆 VERSION 🏆

1.5.0

---

okay that's the whole page, you ate that 🍽️💖. this absolute banger of a manpage is brought to you by Sequoia PGP, version 1.5.0 — literally the same version number as the page itself, matching set, obsessed ✨👑💜. go add some user IDs bestie, and remember: --name and --email, not the combo. periodt. 💅🎀🦋