NAME¶

tss2_authorizepolicy(1) -

SYNOPSIS¶

tss2_authorizepolicy [OPTIONS]

SEE ALSO¶

fapi-config(5) to adjust Fapi parameters like the used cryptographic profile and TCTI or directories for the Fapi metadata storages.

fapi-profile(5) 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 a corresponding PolicyAuthorize elements. The signature is done using 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.

•

-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 tools 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 if specified, or the manpager fails, the short options will be output to stdout.

•

-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.

BUGS¶

Github Issues (https://github.com/tpm2-software/tpm2-tools/issues)

HELP¶

See the Mailing List (https://lists.01.org/mailman/listinfo/tpm2)