1tss2_authorizepolicy(1) General Commands Manual tss2_authorizepolicy(1)
2
3
4
6 tss2_authorizepolicy(1) -
7
9 tss2_authorizepolicy [OPTIONS]
10
12 tss2_authorizepolicy(1) - This command signs a given policy with a giv‐
13 en key such that the policy can be referenced from other policies that
14 contain a corresponding PolicyAuthorize elements.
15
17 These are the available options:
18
19 · -P, --policyPath STRING: Path of the new policy.
20
21 A policyPath is composed of two elements, separated by “/”. A poli‐
22 cyPath starts with “/policy”. The second path element identifies the
23 policy or policy template using a meaningful name.
24
25 · -p, --keyPath STRING: Path of the signing key.
26
27 · -r, --policyRef FILENAME or - (for stdin): A byte buffer to be in‐
28 cluded in the signature. Optional parameter.
29
31 This collection of options are common to all tss2 programs and provide
32 information that many users may expect.
33
34 · -h, --help [man|no-man]: Display the tools manpage. By default, it
35 attempts to invoke the manpager for the tool, however, on failure
36 will output a short tool summary. This is the same behavior if the
37 “man” option argument is specified, however if explicit “man” is re‐
38 quested, the tool will provide errors from man on stderr. If the
39 “no-man” option if specified, or the manpager fails, the short op‐
40 tions will be output to stdout.
41
42 To successfully use the manpages feature requires the manpages to be
43 installed or on MANPATH, See man(1) for more details.
44
45 · -v, --version: Display version information for this tool, supported
46 tctis and exit.
47
49 tss2_authorizepolicy --keyPath HS/SRK/myPolicySignKey --policyPath /policy/pcr-policy --policyRef policyRef.file
50
52 0 on success or 1 on failure.
53
55 Github Issues (https://github.com/tpm2-software/tpm2-tools/issues)
56
58 See the Mailing List (https://lists.01.org/mailman/listinfo/tpm2)
59
60
61
62tpm2-tools APRIL 2019 tss2_authorizepolicy(1)