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

.\" Automatically generated by Pandoc 1.19.2.4
.\"
.TH "tpm2_changeauth" "1" "" "tpm2\-tools" "General Commands Manual"
.hy
.SH NAME
.PP
\f[B]tpm2_changeauth\f[] \- Changes authorization values for TPM
objects.
.SH SYNOPSIS
.PP
\f[B]tpm2_changeauth\f[] [\f[I]OPTIONS\f[]] [\f[I]ARGUMENT\f[]]
.SH DESCRIPTION
.PP
\f[B]tpm2_changeauth\f[] \- Configures authorization values for the
various hierarchies, NV indices, transient and persistent objects.
.PP
Note: For non\-permanent objects (Transient objects and Persistent
objects), copies of the private information (files or persistent
handles) created prior to changing auth are not invalidated.
.SH OPTIONS
.PP
Passwords should follow the "password authorization formatting
standards", see section "Authorization Formatting".
.IP \[bu] 2
\f[B]\-c\f[], \f[B]\-\-object\-context\f[]=\f[I]OBJECT\f[]:
.RS 2
.PP
The key context object to be used for the operation.
.RE
.IP \[bu] 2
\f[B]\-p\f[], \f[B]\-\-object\-auth\f[]=\f[I]AUTH\f[]:
.RS 2
.PP
The old authorization value for the TPM object specified with
\f[B]\-c\f[].
.RE
.IP \[bu] 2
\f[B]\-C\f[], \f[B]\-\-parent\-context\f[]=\f[I]OBJECT\f[]:
.RS 2
.PP
The parent object.
This is required if the object for the operation is a transient or
persistent object.
.RE
.IP \[bu] 2
\f[B]\-r\f[], \f[B]\-\-private\f[]=\f[I]FILE\f[]: The output file which
contains the new sensitive portion of the object whose auth was being
changed.
# Protection Details
.PP
Objects that can move outside of TPM need to be protected
(confidentiality and integrity).
For instance, transient objects require that TPM protected data (key or
seal material) be stored outside of the TPM.
This is seen in tools like tpm2_create(1), where the \f[B]\-r\f[] option
outputs this protected data.
This blob contains the sensitive portions of the object.
The sensitive portions of the object are protected by the parent object,
using the parent\[aq]s symmetric encryption details to encrypt the
sensitive data and HMAC it.
.PP
In\-depth details can be found in sections 23 of:
.IP \[bu] 2
https://trustedcomputinggroup.org/wp\-content/uploads/TPM\-Rev\-2.0\-Part\-1\-Architecture\-01.38.pdf
.PP
Notably Figure 20, is relevant, even though it\[aq]s specifically
referring to duplication blobs, the process is identical.
.PP
If the output is from tpm2_duplicate(1), the output will be slightly
different, as described fully in section 23.
.IP \[bu] 2
\f[B]\-\-cphash\f[]=\f[I]FILE\f[]
.RS 2
.PP
File path to record the hash of the command parameters.
This is commonly termed as cpHash.
NOTE: When this option is selected, The tool will not actually execute
the command, it simply returns a cpHash, unless rphash is also required.
.RE
.IP \[bu] 2
\f[B]\-\-rphash\f[]=\f[I]FILE\f[]
.RS 2
.PP
File path to record the hash of the response parameters.
This is commonly termed as rpHash.
.RE
.IP \[bu] 2
\f[B]\-S\f[], \f[B]\-\-session\f[]=\f[I]FILE\f[]:
.RS 2
.PP
The session created using \f[B]tpm2_startauthsession\f[].
This can be used to specify an auxiliary session for auditing and or
encryption/decryption of the parameters.
.RE
.IP \[bu] 2
\f[B]ARGUMENT\f[] the command line argument specifies the \f[I]AUTH\f[]
to be set for the object specified with \f[B]\-c\f[].
.SS References
.SH Context Object Format
.PP
The type of a context object, whether it is a handle or file name, is
determined according to the following logic \f[I]in\-order\f[]:
.IP \[bu] 2
If the argument is a file path, then the file is loaded as a restored
TPM transient object.
.IP \[bu] 2
If the argument is a \f[I]prefix\f[] match on one of:
.RS 2
.IP \[bu] 2
owner: the owner hierarchy
.IP \[bu] 2
platform: the platform hierarchy
.IP \[bu] 2
endorsement: the endorsement hierarchy
.IP \[bu] 2
lockout: the lockout control persistent object
.RE
.IP \[bu] 2
If the argument argument can be loaded as a number it will be treat as a
handle, e.g.
0x81010013 and used directly.\f[I]OBJECT\f[].
.SH Authorization Formatting
.PP
Authorization for use of an object in TPM2.0 can come in 3 different
forms: 1.
Password 2.
HMAC 3.
Sessions
.PP
\f[B]NOTE:\f[] "Authorizations default to the \f[B]EMPTY PASSWORD\f[]
when not specified".
.SS Passwords
.PP
Passwords are interpreted in the following forms below using prefix
identifiers.
.PP
\f[B]Note\f[]: By default passwords are assumed to be in the string form
when they do not have a prefix.
.SS String
.PP
A string password, specified by prefix "str:" or it\[aq]s absence (raw
string without prefix) is not interpreted, and is directly used for
authorization.
.SS Examples
.IP
.nf
\f[C]
foobar
str:foobar
\f[]
.fi
.SS Hex\-string
.PP
A hex\-string password, specified by prefix "hex:" is converted from a
hexidecimal form into a byte array form, thus allowing passwords with
non\-printable and/or terminal un\-friendly characters.
.SS Example
.IP
.nf
\f[C]
hex:0x1122334455667788
\f[]
.fi
.SS File
.PP
A file based password, specified be prefix "file:" should be the path of
a file containing the password to be read by the tool or a "\-" to use
stdin.
Storing passwords in files prevents information leakage, passwords
passed as options can be read from the process list or common shell
history features.
.SS Examples
.IP
.nf
\f[C]
#\ to\ use\ stdin\ and\ be\ prompted
file:\-

#\ to\ use\ a\ file\ from\ a\ path
file:path/to/password/file

#\ to\ echo\ a\ password\ via\ stdin:
echo\ foobar\ |\ tpm2_tool\ \-p\ file:\-

#\ to\ use\ a\ bash\ here\-string\ via\ stdin:

tpm2_tool\ \-p\ file:\-\ <<<\ foobar
\f[]
.fi
.SS Sessions
.PP
When using a policy session to authorize the use of an object, prefix
the option argument with the \f[I]session\f[] keyword.
Then indicate a path to a session file that was created with
tpm2_startauthsession(1).
Optionally, if the session requires an auth value to be sent with the
session handle (eg policy password), then append a + and a string as
described in the \f[B]Passwords\f[] section.
.SS Examples
.PP
To use a session context file called \f[I]session.ctx\f[].
.IP
.nf
\f[C]
session:session.ctx
\f[]
.fi
.PP
To use a session context file called \f[I]session.ctx\f[] \f[B]AND\f[]
send the authvalue mypassword.
.IP
.nf
\f[C]
session:session.ctx+mypassword
\f[]
.fi
.PP
To use a session context file called \f[I]session.ctx\f[] \f[B]AND\f[]
send the \f[I]HEX\f[] authvalue 0x11223344.
.IP
.nf
\f[C]
session:session.ctx+hex:11223344
\f[]
.fi
.SS PCR Authorizations
.PP
You can satisfy a PCR policy using the "pcr:" prefix and the PCR
minilanguage.
The PCR minilanguage is as follows:
\f[C]<pcr\-spec>=<raw\-pcr\-file>\f[]
.PP
The PCR spec is documented in in the section "PCR bank specifiers".
.PP
The \f[C]raw\-pcr\-file\f[] is an \f[B]optional\f[] the output of the
raw PCR contents as returned by \f[I]tpm2_pcrread(1)\f[].
.PP
PCR bank specifiers (common/pcr.md)
.SS Examples
.PP
To satisfy a PCR policy of sha256 on banks 0, 1, 2 and 3 use a specifier
of:
.IP
.nf
\f[C]
pcr:sha256:0,1,2,3
\f[]
.fi
.PP
specifying \f[I]AUTH\f[].
.SH COMMON OPTIONS
.PP
This collection of options are common to many 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 man(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.
.IP \[bu] 2
\f[B]\-V\f[], \f[B]\-\-verbose\f[]: Increase the information that the
tool prints to the console during its execution.
When using this option the file and line number are printed.
.IP \[bu] 2
\f[B]\-Q\f[], \f[B]\-\-quiet\f[]: Silence normal tool output to stdout.
.IP \[bu] 2
\f[B]\-Z\f[], \f[B]\-\-enable\-errata\f[]: Enable the application of
errata fixups.
Useful if an errata fixup needs to be applied to commands sent to the
TPM.
Defining the environment TPM2TOOLS_ENABLE_ERRATA is equivalent.
information many users may expect.
.SH TCTI Configuration
.PP
The TCTI or "Transmission Interface" is the communication mechanism with
the TPM.
TCTIs can be changed for communication with TPMs across different
mediums.
.PP
To control the TCTI, the tools respect:
.IP "1." 3
The command line option \f[B]\-T\f[] or \f[B]\-\-tcti\f[]
.IP "2." 3
The environment variable: \f[I]TPM2TOOLS_TCTI\f[].
.PP
\f[B]Note:\f[] The command line option always overrides the environment
variable.
.PP
The current known TCTIs are:
.IP \[bu] 2
tabrmd \- The resource manager, called
tabrmd (https://github.com/tpm2-software/tpm2-abrmd).
Note that tabrmd and abrmd as a tcti name are synonymous.
.IP \[bu] 2
mssim \- Typically used for communicating to the TPM software simulator.
.IP \[bu] 2
device \- Used when talking directly to a TPM device file.
.IP \[bu] 2
none \- Do not initalize a connection with the TPM.
Some tools allow for off\-tpm options and thus support not using a TCTI.
Tools that do not support it will error when attempted to be used
without a TCTI connection.
Does not support \f[I]ANY\f[] options and \f[I]MUST BE\f[] presented as
the exact text of "none".
.PP
The arguments to either the command line option or the environment
variable are in the form:
.PP
\f[C]<tcti\-name>:<tcti\-option\-config>\f[]
.PP
Specifying an empty string for either the \f[C]<tcti\-name>\f[] or
\f[C]<tcti\-option\-config>\f[] results in the default being used for
that portion respectively.
.SS TCTI Defaults
.PP
When a TCTI is not specified, the default TCTI is searched for using
\f[I]dlopen(3)\f[] semantics.
The tools will search for \f[I]tabrmd\f[], \f[I]device\f[] and
\f[I]mssim\f[] TCTIs \f[B]IN THAT ORDER\f[] and \f[B]USE THE FIRST ONE
FOUND\f[].
You can query what TCTI will be chosen as the default by using the
\f[B]\-v\f[] option to print the version information.
The "default\-tcti" key\-value pair will indicate which of the
aforementioned TCTIs is the default.
.SS Custom TCTIs
.PP
Any TCTI that implements the dynamic TCTI interface can be loaded.
The tools internally use \f[I]dlopen(3)\f[], and the raw
\f[I]tcti\-name\f[] value is used for the lookup.
Thus, this could be a path to the shared library, or a library name as
understood by \f[I]dlopen(3)\f[] semantics.
.SH TCTI OPTIONS
.PP
This collection of options are used to configure the various known TCTI
modules available:
.IP \[bu] 2
\f[B]device\f[]: For the device TCTI, the TPM character device file for
use by the device TCTI can be specified.
The default is \f[I]/dev/tpm0\f[].
.RS 2
.PP
Example: \f[B]\-T device:/dev/tpm0\f[] or \f[B]export
\f[I]TPM2TOOLS_TCTI\f[]="device:/dev/tpm0"\f[]
.RE
.IP \[bu] 2
\f[B]mssim\f[]: For the mssim TCTI, the domain name or IP address and
port number used by the simulator can be specified.
The default are 127.0.0.1 and 2321.
.RS 2
.PP
Example: \f[B]\-T mssim:host=localhost,port=2321\f[] or \f[B]export
\f[I]TPM2TOOLS_TCTI\f[]="mssim:host=localhost,port=2321"\f[]
.RE
.IP \[bu] 2
\f[B]abrmd\f[]: For the abrmd TCTI, the configuration string format is a
series of simple key value pairs separated by a \[aq],\[aq] character.
Each key and value string are separated by a \[aq]=\[aq] character.
.RS 2
.IP \[bu] 2
TCTI abrmd supports two keys:
.RS 2
.IP "1." 3
\[aq]bus_name\[aq] : The name of the tabrmd service on the bus (a
string).
.IP "2." 3
\[aq]bus_type\[aq] : The type of the dbus instance (a string) limited to
\[aq]session\[aq] and \[aq]system\[aq].
.RE
.PP
Specify the tabrmd tcti name and a config string of
\f[C]bus_name=com.example.FooBar\f[]:
.PP
\f[C]\\\-\-tcti=tabrmd:bus_name=com.example.FooBar\f[]
.PP
Specify the default (abrmd) tcti and a config string of
\f[C]bus_type=session\f[]:
.PP
\f[C]\\\-\-tcti:bus_type=session\f[]
.PP
\f[B]NOTE\f[]: abrmd and tabrmd are synonymous.
the various known TCTI modules.
.RE
.SH EXAMPLES
.SS Set owner, endorsement and lockout authorizations to newpass
.IP
.nf
\f[C]
tpm2_changeauth\ \-c\ owner\ newpass
tpm2_changeauth\ \-c\ endorsement\ newpass
tpm2_changeauth\ \-c\ lockout\ newpass
\f[]
.fi
.SS Change owner, endorsement and lockout authorizations
.IP
.nf
\f[C]
tpm2_changeauth\ \-c\ o\ \-p\ newpass\ newerpass
tpm2_changeauth\ \-c\ e\ \-p\ newpass\ newerpass
tpm2_changeauth\ \-c\ l\ \-p\ newpass\ newerpass
\f[]
.fi
.SS Set owner authorization to empty password
.IP
.nf
\f[C]
tpm2_changeauth\ \-c\ o\ \-p\ oldpass
\f[]
.fi
.SS Modify authorization for a loadable transient object
.IP
.nf
\f[C]
tpm2_createprimary\ \-Q\ \-C\ o\ \-c\ prim.ctx

tpm2_create\ \-Q\ \-g\ sha256\ \-G\ aes\ \-u\ key.pub\ \-r\ key.priv\ \-C\ prim.ctx

tpm2_load\ \-C\ prim.ctx\ \-u\ key.pub\ \-r\ key.priv\ \-n\ key.name\ \-c\ key.ctx

tpm2_changeauth\ \-c\ key.ctx\ \-C\ prim.ctx\ \-r\ key.priv\ newkeyauth
\f[]
.fi
.SS Modify authorization for a NV Index
.PP
Requires Extended Session Support.
.IP
.nf
\f[C]
tpm2_startauthsession\ \-S\ session.ctx

tpm2_policycommandcode\ \-S\ session.ctx\ \-L\ policy.nvchange\ TPM2_CC_NV_ChangeAuth
tpm2_flushcontext\ session.ctx

NVIndex=0x1500015
tpm2_nvdefine\ \ \ $NVIndex\ \-C\ o\ \-s\ 32\ \-a\ "authread|authwrite"\ \-L\ policy.nvchange
tpm2_startauthsession\ \\\-\-policy\-session\ \-S\ session.ctx

tpm2_policycommandcode\ \-S\ session.ctx\ \-L\ policy.nvchange\ TPM2_CC_NV_ChangeAuth

tpm2_changeauth\ \-p\ session:session.ctx\ \-c\ $NVIndex\ newindexauth
\f[]
.fi
.SH Returns
.PP
Tools can return any of the following codes:
.IP \[bu] 2
0 \- Success.
.IP \[bu] 2
1 \- General non\-specific error.
.IP \[bu] 2
2 \- Options handling error.
.IP \[bu] 2
3 \- Authentication error.
.IP \[bu] 2
4 \- TCTI related error.
.IP \[bu] 2
5 \- Non supported scheme.
Applicable to tpm2_testparams.
.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)