rsop-update-key(1)

πŸ“¦
version 0.12.0 Β· 2 versions
, in arch rolling

okay bestie, you're reading rsop-update-key(1) from the General Commands Manual 🫢 buckle up, it's a short one and it's lowkey iconic.

πŸ’– NAME πŸ’–

rsop-update-key β€” Keep a Secret Key Up-To-Date. That's the whole vibe: the name, the mission, the slay.

✨ SYNOPSIS ✨

Here's the exact shape of it, no cap:

rsop 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. That's the assignment. The command is here to keep a Secret Key up-to-date, and honestly? main character energy πŸ’….

πŸ’… OPTIONS πŸ’…

okay so these are the flags, and every single one matters:

  • --debug β€” Emit verbose output for debugging. It's giving receipts, bestie πŸ”.
  • --no-armor β€” Don't ASCII-armor output. If you don't want the armor, this is your girl ✨.
  • --signing-only β€” Don't make the updated key encryption-capable if it isn't already. Keeping it signing-only, periodt πŸŽ€.
  • --no-added-capabilities β€” Don't advertise support for capabilities that aren't already advertised by the key. No extra flexing, no cap πŸ’….
  • --with-key-password <WITH_KEY_PASSWORD> β€” Unlock the keys with these passwords. Yes, the placeholder is literally <WITH_KEY_PASSWORD> πŸ”‘.
  • --merge-certs <MERGE_CERTS> β€” Merge updates into the key. The placeholder is literally <MERGE_CERTS> πŸŽ€.
  • -h, --help β€” Print help. When in doubt, ask for help, bestie 🫢.

mwah πŸ’‹ that's the page β€” brought to you by rsop 0.12.0, dated February 2025. bye bestie, go keep that key up-to-date 🌈✨

πŸ“¦ where this page comes from
  • arch rolling: rsop 0.12.0-1 Β· Apache-2.0 OR MIT AND CC0-1.0
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms