SKOPEO-GENERATE-SIGSTORE-KEY(1)

💅 skopeo-generate-sigstore-key

okay bestie, so this is a page from the skopeo manual — like, the skopeo family of man pages, iykyk — and this one is all about making yourself a sigstore key pair. Yes, a public key AND a private key, one each, a matching set. Iconic. 🎀

---

✨ NAME ✨

skopeo-generate-sigstore-key — generate a sigstore public/private key pair.

---

🦋 SYNOPSIS 🦋

skopeo generate-sigstore-key [options] --output-prefix prefix

---

🌸 DESCRIPTION 🌸

So basically this command generates a public/private key pair, and the whole point of that pair is signing sigstore image signatures. That's the vibe. 🔥

The private key is encrypted with a passphrase — and here's the cute part — if you don't hand over a passphrase using an option, the command will just prompt you for it interactively. Very "it'll ask you when it needs to know" of it. 💖

The private key gets written to prefix.private. The public key gets written to prefix.pub. Two files, one prefix, matching names, slay. 🌈

---

🧚 OPTIONS 🧚

Also, ngl, for the options that go before the subcommand name, go check out skopeo(1). That's where those live. 🫶

• --help, -h — prints the usage statement. standard, but we love her. ✨
• --output-prefix prefix — Mandatory, bestie. This is the path prefix for your output keys, and it turns into prefix.private and prefix.pub. No prefix, no keys. periodt. 💅
• --passphrase-file path — the passphrase used to encrypt the private key lives in this file. Only the first line gets read, okay? Just the first one. And listen — a passphrase stored in a file is of, like, questionable security if other users can read that file. Lowkey risky. The manpage is fr fr telling you: do not use this option if at all avoidable. 🙈

⚠️ Like, genuinely: storing your passphrase in a readable file is a security question mark. Only use --passphrase-file if there's literally no other way.

---

💜 EXAMPLES 💜

$ skopeo generate-sigstore-key --output-prefix mykey

---

👑 SEE ALSO 👑

skopeo(1), skopeo-copy(1), containers-policy.json(5)

---

💀 AUTHORS 💀

Miloslav Trmač <mitr@redhat.com> ⟨mailto:mitr@redhat.com⟩

---

okay that's the whole page, you ate that 🍓 — this one's from the skopeo-generate-sigstore-key(1) manual, same title on the header and the footer because that's just how man pages do, and the footer's date/version is right there with it. mwah 💋🌸