tss2_authorizepolicy(1)

🌸 NAME 🌸

tss2_authorizepolicy(1) β€” okay bestie, this is the page for this command, straight outta the General Commands Manual. ✨


✨ SYNOPSIS ✨

tss2_authorizepolicy [OPTIONS]

πŸ‘€ SEE ALSO πŸ‘€

  • fapi-config(5) β€” use this to adjust Fapi parameters like the used cryptographic profile and TCTI, or directories for the Fapi metadata storages. πŸŽ€
  • fapi-profile(5) β€” use this to determine the cryptographic algorithms and parameters for all keys and operations of a specific TPM interaction, like the name hash algorithm, the asymmetric signature algorithm, scheme and parameters, and PCR bank selection. πŸ¦‹

πŸ’… DESCRIPTION πŸ’…

tss2_authorizepolicy(1) β€” this command signs a given policy with a given key such that the policy can be referenced from other policies that contain corresponding PolicyAuthorize elements. No cap, it's literally doing the signature with the TPM signing schemes as specified in the cryptographic profile (cf., fapi-profile(5)). πŸ”₯


πŸŽ€ OPTIONS πŸŽ€

These are the available options:

  • -P, --policyPath=STRING β€” path of the new policy.

A policyPath is composed of two elements, separated by /. A policyPath starts with /policy. The second path element identifies the policy or policy template using a meaningful name. πŸ’–

  • -p, --keyPath=STRING β€” path of the signing key. πŸ”‘
  • -r, --policyRef=FILENAME or - (for stdin) β€” a byte buffer to be included in the signature. Optional parameter. πŸŽ€

🌈 COMMON OPTIONS 🌈

This collection of options are common to all tss2 programs and provide information that many users may expect. 🫢

  • -h, --help [man|no-man] β€” display the tool's manpage. By default, it attempts to invoke the manpager for the tool, however, on failure will output a short tool summary. This is the same behavior if the man option argument is specified, however if explicit man is requested, the tool will provide errors from man on stderr. If the no-man option is specified, or the manpager fails, the short options will be output to stdout.
to successfully use the manpages feature requires the manpages to be installed or on MANPATH. See man(1) for more details. 🧚
  • -v, --version β€” display version information for this tool, supported tctis and exit. ⭐

πŸ¦‹ EXAMPLE πŸ¦‹

tss2_authorizepolicy --keyPath=HS/SRK/myPolicySignKey --policyPath=/policy/pcr-policy --policyRef=policyRef.file

⭐ RETURNS ⭐

0 on success or 1 on failure. Periodt. πŸ’…


πŸ’€ BUGS πŸ’€

Github Issues


🫢 HELP 🫢

See the Mailing List


πŸ“œ License πŸ“œ

This work is licensed under the Creative Commons Attribution 4.0 International License (CC BY 4.0).

mwah πŸ’‹ this iconic page is from tpm2-tools, APRIL 2019 β€” periodt, bestie. πŸ’–πŸŽ€

πŸ“¦ where this page comes from