tss2_policyexport(1)

πŸ’… tss2_policyexport(1) β€” ur girl's guide to exporting policies ✨

okay so real quick: this is a page from the General Commands Manual, and yes bestie, it's a whole vibe. sit down, grab a strawberry drink πŸ“, and let's get into it.


🌸 NAME 🌸

tss2_policyexport(1) β€” that's literally the whole name section, no cap. she's minimal, she's iconic, she's giving less-is-more. πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

tss2_policyexport [OPTIONS]

that's it. that's the whole incantation. options go in, magic comes out. πŸ’«


πŸ‘‘ SEE ALSO πŸ‘‘

like, go read these too, they're the supporting cast and they ate:

  • fapi-config(5) β€” use this one to adjust Fapi parameters, like which cryptographic profile is getting used, the TCTI, or the directories for the Fapi metadata storages. very much the settings girlie. 🧚
  • fapi-profile(5) β€” this one's for pinning down the cryptographic algorithms and parameters for all keys and operations of a specific TPM interaction. think: the name hash algorithm, the asymmetric signature algorithm, the scheme and its parameters, and PCR bank selection. iykyk. πŸ”₯

✨ DESCRIPTION ✨

tss2_policyexport(1) β€” okay so what does she actually do? she exports a policy associated with a key, and she does it in JSON encoding. that's the whole assignment and she understood it. πŸ’…


πŸ’– OPTIONS πŸ’–

these are the available options, bestie, and there are only three so you literally have no excuse:

  • -f, --force β€” force overwriting the output file. she will not ask, she will not hesitate, she will simply replace. 😭
  • -o, --jsonPolicy=FILENAME or - (for stdout) β€” returns the JSON-encoded policy. and yes, you can pass - to yeet it straight to stdout instead of a file. 🫢
  • -p, --path=STRING β€” the path of the key. that's the one. 🌈

πŸŽ€ COMMON OPTIONS πŸŽ€

this collection of options is common to all tss2 programs and provides info that many users may expect. so like, the shared lore. πŸ“š

  • -h, --help [man|no-man] β€” displays the tool's manpage. by default it attempts to invoke the manpager for the tool, but on failure it'll output a short tool summary. same behavior if you specify the man option argument β€” except if explicit man is requested, the tool will provide errors from man on stderr. if you specify the no-man option, or the manpager just gives up, the short options get output to stdout.
to successfully use the manpages feature you need the manpages installed, or on MANPATH. see man(1) for more details. no manpages, no slay. πŸ™ˆ
  • -v, --version β€” displays version information for this tool and supported tctis, then exits. a little goodbye kiss. πŸ’‹

πŸ”₯ EXAMPLE πŸ”₯

steal this, it's cute:

tss2_exportpolicy --path=HS/SRK/myRSASign --jsonPolicy=jsonPolicy.json

⭐ RETURNS ⭐

0 on success or 1 on failure. binary queen. either she ate or she didn't. πŸ’€


πŸ’œ BUGS πŸ’œ

Github Issues. that's where the drama goes. πŸ‘€


🌈 HELP 🌈

See the Mailing List. the group chat, essentially. πŸ’¬


🧚 License 🧚

This work is licensed under the Creative Commons Attribution 4.0 International License (CC BY 4.0). share the love, credit the girls. 🫢


and that's the whole page! brought to you by tpm2-tools, dated APRIL 2019 β€” a classic, an era, a moment. mwah. πŸ’‹βœ¨πŸŽ€

πŸ“¦ where this page comes from