csu3_am335x/EVSE/GPL/tpm2-tools-5.1/man/man1/tss2_authorizepolicy.1

.\" Automatically generated by Pandoc 1.19.2.4
.\"
.TH "tss2_authorizepolicy" "1" "APRIL 2019" "tpm2\-tools" "General Commands Manual"
.hy
.SH NAME
.PP
\f[B]tss2_authorizepolicy\f[](1) \-
.SH SYNOPSIS
.PP
\f[B]tss2_authorizepolicy\f[] [\f[I]OPTIONS\f[]]
.SH SEE ALSO
.PP
\f[B]fapi\-config(5)\f[] to adjust Fapi parameters like the used
cryptographic profile and TCTI or directories for the Fapi metadata
storages.
.PP
\f[B]fapi\-profile(5)\f[] 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.
.SH DESCRIPTION
.PP
\f[B]tss2_authorizepolicy\f[](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., \f[B]fapi\-profile(5)\f[]).
.SH OPTIONS
.PP
These are the available options:
.IP \[bu] 2
\f[B]\-P\f[], \f[B]\-\-policyPath\f[]=\f[I]STRING\f[]: Path of the new
policy.
.RS 2
.PP
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.
.RE
.IP \[bu] 2
\f[B]\-p\f[], \f[B]\-\-keyPath\f[]=\f[I]STRING\f[]: Path of the signing
key.
.IP \[bu] 2
\f[B]\-r\f[], \f[B]\-\-policyRef\f[]=\f[I]FILENAME\f[] or \f[I]\-\f[]
(for stdin): A byte buffer to be included in the signature.
Optional parameter.
.SH COMMON OPTIONS
.PP
This collection of options are common to all tss2 programs and provide
information that many users may expect.
.IP \[bu] 2
\f[B]\-h\f[], \f[B]\-\-help [man|no\-man]\f[]: 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.
.RS 2
.PP
To successfully use the manpages feature requires the manpages to be
installed or on \f[I]MANPATH\f[], See \f[B]man\f[](1) for more details.
.RE
.IP \[bu] 2
\f[B]\-v\f[], \f[B]\-\-version\f[]: Display version information for this
tool, supported tctis and exit.
.SH EXAMPLE
.IP
.nf
\f[C]
tss2_authorizepolicy\ \-\-keyPath=HS/SRK/myPolicySignKey\ \-\-policyPath=/policy/pcr\-policy\ \-\-policyRef=policyRef.file
\f[]
.fi
.SH RETURNS
.PP
0 on success or 1 on failure.
.SH BUGS
.PP
Github Issues (https://github.com/tpm2-software/tpm2-tools/issues)
.SH HELP
.PP
See the Mailing List (https://lists.01.org/mailman/listinfo/tpm2)