POLICYNV(1)

✨ NAME ✨

policynv — she Runs TPM2_PolicyNv 💅 and that's literally it, that's the whole job description. It's a User Commands page, section 1, you know the drill 🫶

---

🎀 DESCRIPTION 🎀

okay bestie, before we do anything else, the page just opens with this:

--version-string=v1045 is not a valid option

and honestly? not me getting personally read by a manpage first sentence in 💀 noted, moving on.

Then it's like:

policynv

Runs TPM2_PolicyNV

       [-hi hierarchy authHandle (o, p)]

       default NV index

-ha NV index handle (operand A)

       [-pwda password for authorization (default empty)] -hs policy
       session handle -ic data string (operandB) -if data file
       (operandB) [-off offset (default 0)] -op operation (default A =
       B)

so real quick, translating the group chat:

• -hi takes a hierarchy authHandle, and it's marked (o, p) — you're getting the o and p energy 🦋
• the default NV index is just... the default. no thoughts, head empty, that's the vibe.
• -ha is the NV index handle, and she's operand A in the whole comparison drama 👑
• -pwda — password for authorization, and the default is empty (default empty)
• -hs — policy session handle
• -ic — data string, which is operandB
• -if — data file, also operandB
• -off — offset, default 0
• -op — operation, and the default is A = B

and the operations?? there are twelve of them, she's thorough:

• 0 — A = B
• 1 — A != B
• 2 — A > B signed
• 3 — A > B unsigned
• 4 — A < B signed
• 5 — A < B unsigned
• 6 — A >= B signed
• 7 — A >= B unsigned
• 8 — A <= B signed
• 9 — A <= B unsigned
• A — All bits SET in B are SET in A. ((A&B)=B)
• B — All bits SET in B are CLEAR in A. ((A&B)=0)

obsessed with how A and B show up as operation names and as operand names, truly main character energy, they contain multitudes 💖

then the session bit:

• -se[0-2] — session handle / attributes, and the default is PWAP

and the attributes are:

01 continue 20 command decrypt 40 response encrypt

slay. and then, because the universe loves a cliffhanger:

--version is not a valid option

😭 okay?? we heard you the first time, respectfully.

AND THEN THE WHOLE THING HAPPENS AGAIN. no cap, fr fr, the entire block from policynv / Runs TPM2_PolicyNV down through -se[0-2], the attributes line, and --version is not a valid option shows up a second time. Not me double-checking whether I scrolled up 💀 but nope, it's really in there twice, so here it is twice, because I do not skip details in this house:

policynv

Runs TPM2_PolicyNV

       [-hi hierarchy authHandle (o, p)]

       default NV index

-ha NV index handle (operand A)

       [-pwda password for authorization (default empty)] -hs policy
       session handle -ic data string (operandB) -if data file
       (operandB) [-off offset (default 0)] -op operation (default A =
       B)

• 0 — A = B
• 1 — A != B
• 2 — A > B signed
• 3 — A > B unsigned
• 4 — A < B signed
• 5 — A < B unsigned
• 6 — A >= B signed
• 7 — A >= B unsigned
• 8 — A <= B signed
• 9 — A <= B unsigned
• A — All bits SET in B are SET in A. ((A&B)=B)
• B — All bits SET in B are CLEAR in A. ((A&B)=0)

and again, one more time for the people in the back:

• -se[0-2] — session handle / attributes, default PWAP

01 continue 20 command decrypt 40 response encrypt

--version is not a valid option

there we go. we survived. vibe check: passed ✨

---

🦋 SEE ALSO 🦋

bestie the full tea is maintained as a Texinfo manual 🧚 and if the info and policynv programs are properly installed at your site, this command:

info policynv

should give you access to the complete manual. go get your lore 📖

---

and that's the whole page!! 💜 this was policynv, from the July 2017 era, living under the POLICYNV(1) banner — she's an icon, she's a legend, and she is the moment, periodt 👑🌸