sqop-update-key(1)

✨ sqop-update-key — keeping your secret key fresh, bestie ✨

Okay so real talk: this is sqop-update-key, living in the General Commands Manual section of the sqop family, and its whole entire job is Keep a Secret Key Up-To-Date. That's it. That's the gig. Your key stays current, you stay unbothered. 💅

---

🌸 SYNOPSIS 🌸

sqop update-key [--debug] [--no-armor] [--signing-only]
[--no-added-capabilities] [--with-key-password] [--merge-certs]
[-h|--help]

---

💖 DESCRIPTION 💖

Keep a Secret Key Up-To-Date 🫶

(Yes, that's literally the whole description. She said what she said. The vibe is the point.)

---

✨ OPTIONS ✨

• --debug — Emit verbose output for debugging. It's giving "tell me everything", and honestly? We love a key that overshares. 🐛
• --no-armor — Don't ASCII-armor output. Raw output, no cute lil' -----BEGIN wrapper, no frills. 😤
• --signing-only — Don't make the updated key encryption-capable if it isn't already. If it wasn't about that encryption life before, we're not forcing it into one now. 💀
• --no-added-capabilities — Don't advertise support for capabilities that aren't already advertised by the key. No flexing new powers it never claimed, periodt. 👑
• --with-key-password <WITH_KEY_PASSWORD> — Unlock the keys with these passwords. Drop the password(s) in here so the keys can actually, y'know, open up. 🔑
• --merge-certs <MERGE_CERTS> — Merge updates into the key. Squish the new stuff in with the old stuff, bestie. 🧚
• -h, --help — Print help. Classic. The "wait what do I type again" button, and it always comes through. 🌈

---

Heads up, gorgeous: the synopsis shows --with-key-password and --merge-certs as flags with values, so give 'em their <WITH_KEY_PASSWORD> and <MERGE_CERTS> arguments — don't leave them hanging. 🙈

---

That's the whole page, no notes. This lil' beauty ships as sqop 0.38.0, dated February 2025, and it lives under the manual name sqop-update-key(1). Go keep that secret key up-to-date, main character. ✨🎀🦋