oct-admin-...n-validity(1)

💅 oct-admin-signing-pin-validity(1) — the glow-up version

okay so bestie, welcome to the General Commands Manual entry for oct-admin-signing-pin-validity(1) — yes the header is literally truncated with ... in the source and we're just gonna vibe with it ✨

---

🌸 NAME 🌸

oct-admin-signing-pin-validity — tell your device whether showing the user PIN is a one-time thing or a forever thing 🫶

🎀 SYNOPSIS 🎀

oct admin signing-pin-validity [-h|--help] <STATE>

🦋 DESCRIPTION 🦋

okay so this is the command where you configure if user PIN presentation is valid for just one signing operation, or for unlimited signing operations. that's the whole plot 💅

fr fr, what it actually does is set the "only valid for one PSO:CDS" setting in PW Status Bytes. that's the switch you're flipping, no cap.

🔥 OPTIONS 🔥

• -h, --help — print help (see a summary with -h) 👑 tiny help vs. deluxe help, both iconic
• <STATE> — the validity of user PIN presentation for signing operations. this is the main character argument, choose wisely 😭

possible values:

• once — one and done, one signing operation only 🍓
• unlimited — go off, unlimited signing operations, no limits bestie 🌈

ngl, these two values are the entire vibe check for this command — it's giving "binary choice, big consequences" 💀

---

💜 cute lil sign-off 💜

this page lives under the oct-admin-...n-validity(1) name (the title's a little mangled at the edges, we stan anyway 🙈), and the footer of the original is honestly a bit of a mess — it reads oct-admin-signing-pin-validitoct-admin-...n-validity(1), which is just the page name and header smushed together with no clean version or date to hand you. so: no version number, no date, just vibes and a manual name 🧚‍♀️ mwah 💖