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

.\" Automatically generated by Pandoc 1.19.2.4
.\"
.TH "tpm2_create" "1" "" "tpm2\-tools" "General Commands Manual"
.hy
.SH NAME
.PP
\f[B]tpm2_create\f[](1) \- Create a child object.
.SH SYNOPSIS
.PP
\f[B]tpm2_create\f[] [\f[I]OPTIONS\f[]]
.SH DESCRIPTION
.PP
\f[B]tpm2_create\f[](1) \- Create a child object.
The object can either be a key or a sealing object.
A sealing object allows to seal user data to the TPM, with a maximum
size of 128 bytes.
Additionally it will load the created object if the \f[B]\-c\f[] is
specified.
.SH OPTIONS
.PP
These options for creating the TPM entity:
.IP \[bu] 2
\f[B]\-C\f[], \f[B]\-\-parent\-context\f[]=\f[I]OBJECT\f[]:
.RS 2
.PP
The parent of the object to be created.
.RE
.IP \[bu] 2
\f[B]\-P\f[], \f[B]\-\-parent\-auth\f[]=\f[I]AUTH\f[]:
.RS 2
.PP
The authorization value of the parent object specified with
\f[B]\-C\f[].
.RE
.IP \[bu] 2
\f[B]\-p\f[], \f[B]\-\-key\-auth\f[]=\f[I]AUTH\f[]:
.RS 2
.PP
The authorization value for the created object.
.RE
.IP \[bu] 2
\f[B]\-g\f[], \f[B]\-\-hash\-algorithm\f[]=\f[I]ALGORITHM\f[]:
.RS 2
.PP
The hash algorithm for generating the objects name.
This is optional and defaults to sha256 when not specified.
.RE
.IP \[bu] 2
\f[B]\-G\f[], \f[B]\-\-key\-algorithm\f[]=\f[I]ALGORITHM\f[]:
.RS 2
.PP
The key algorithm associated with this object.
It defaults to "rsa" if not specified.
.RE
.IP \[bu] 2
\f[B]\-a\f[], \f[B]\-\-attributes\f[]=\f[I]ATTRIBUTES\f[]:
.RS 2
.PP
The object attributes, optional.
The default for created objects is:
.PP
\f[C]TPMA_OBJECT_SIGN_ENCRYPT|TPMA_OBJECT_DECRYPT|TPMA_OBJECT_FIXEDTPM|\ \ TPMA_OBJECT_FIXEDPARENT|TPMA_OBJECT_SENSITIVEDATAORIGIN|\ \ TPMA_OBJECT_USERWITHAUTH\f[]
.PP
When \f[B]\-i\f[] is specified for sealing,
\f[C]TPMA_OBJECT_SIGN_ENCRYPT\f[] and \f[C]TPMA_OBJECT_DECRYPT\f[] are
removed from the default attribute set.
The algorithm is set in a way where the the object is only good for
sealing and unsealing.
I.e.
one cannot use an object for sealing and cryptography operations.
.PP
When \f[B]\-L\f[] is specified for adding policy based authorization
information AND no string password is specified, the attribute
\f[C]TPMA_OBJECT_USERWITHAUTH\f[] is cleared unless an explicit choice
is made by setting of the attribute with \f[B]\-a\f[] option.
This prevents creation of objects with inadvertant auth model where in
user intended to enforce a policy but inadvertantly created an object
with empty auth which can be used instead of policy authorization.
.RE
.IP \[bu] 2
\f[B]\-i\f[], \f[B]\-\-sealing\-input\f[]=\f[I]FILE\f[] or
\f[I]STDIN\f[]:
.RS 2
.PP
The data file to be sealed, optional.
If file is \-, read from stdin.
When sealing data only the \f[I]TPM_ALG_KEYEDHASH\f[] algorithm with a
NULL scheme is allowed.
Thus, \f[B]\-G\f[] cannot be specified.
.RE
.IP \[bu] 2
\f[B]\-L\f[], \f[B]\-\-policy\f[]=\f[I]FILE\f[]:
.RS 2
.PP
The input policy file, optional.
.RE
.IP \[bu] 2
\f[B]\-u\f[], \f[B]\-\-public\f[]=\f[I]FILE\f[]:
.RS 2
.PP
The output file which contains the public portion of the created object,
optional.
.RE
.IP \[bu] 2
\f[B]\-r\f[], \f[B]\-\-private\f[]=\f[I]FILE\f[]:
.RS 2
.PP
The output file which contains the sensitive portion of the object,
optional.
# Protection Details
.RE
.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]\-c\f[], \f[B]\-\-key\-context\f[]=\f[I]FILE\f[]:
.RS 2
.PP
The output file which contains the key context, optional.
The key context is analogous to the context file produced by
\f[B]tpm2_load\f[](1), however is generated via a
\f[B]tpm2_createloaded\f[](1) command.
This option can be used to avoid the normal \f[B]tpm2_create\f[](1) and
\f[B]tpm2_load\f[](1) command sequences and do it all in one command,
atomically.
.RE
.IP \[bu] 2
\f[B]\-\-creation\-data\f[]=\f[I]FILE\f[]:
.RS 2
.PP
An optional file output that saves the creation data for certification.
.IP \[bu] 2
\f[B]\-\-template\-data\f[]=\f[I]FILE\f[]:
.PP
An optional file output that saves the key template data (TPM2B_PUBLIC)
to be used in \f[B]tpm2_policytemplate\f[].
.RE
.IP \[bu] 2
\f[B]\-t\f[], \f[B]\-\-creation\-ticket\f[]=\f[I]FILE\f[]:
.RS 2
.PP
An optional file output that saves the creation ticket for
certification.
.RE
.IP \[bu] 2
\f[B]\-d\f[], \f[B]\-\-creation\-hash\f[]=\f[I]FILE\f[]:
.RS 2
.PP
An optional file output that saves the creation hash for certification.
.RE
.IP \[bu] 2
\f[B]\-q\f[], \f[B]\-\-outside\-info\f[]=\f[I]HEX_STR_OR_FILE\f[]:
.RS 2
.PP
An optional hex string or path to add unique data to the creation data.
Note that it does not contribute in creating statistically unique
object.
.RE
.IP \[bu] 2
\f[B]\-l\f[], \f[B]\-\-pcr\-list\f[]=\f[I]PCR\f[]:
.RS 2
.PP
The list of PCR banks and selected PCRs\[aq] ids for each bank to be
included in the creation data for certification.
.RE
.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.
.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[].
Multiple of these can be specified.
For example, you can have one session for auditing and another for
encryption/decryption of the parameters.
.RE
.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 Algorithm Specifiers
.PP
Options that take algorithms support "nice\-names".
.PP
There are two major algorithm specification string classes, simple and
complex.
Only certain algorithms will be accepted by the TPM, based on usage and
conditions.
.SS Simple specifiers
.PP
These are strings with no additional specification data.
When creating objects, non\-specified portions of an object are assumed
to defaults.
You can find the list of known "Simple Specifiers Below".
.SS Asymmetric
.IP \[bu] 2
rsa
.IP \[bu] 2
ecc
.SS Symmetric
.IP \[bu] 2
aes
.IP \[bu] 2
camellia
.SS Hashing Algorithms
.IP \[bu] 2
sha1
.IP \[bu] 2
sha256
.IP \[bu] 2
sha384
.IP \[bu] 2
sha512
.IP \[bu] 2
sm3_256
.IP \[bu] 2
sha3_256
.IP \[bu] 2
sha3_384
.IP \[bu] 2
sha3_512
.SS Keyed Hash
.IP \[bu] 2
hmac
.IP \[bu] 2
xor
.SS Signing Schemes
.IP \[bu] 2
rsassa
.IP \[bu] 2
rsapss
.IP \[bu] 2
ecdsa
.IP \[bu] 2
ecdaa
.IP \[bu] 2
ecschnorr
.SS Asymmetric Encryption Schemes
.IP \[bu] 2
oaep
.IP \[bu] 2
rsaes
.IP \[bu] 2
ecdh
.SS Modes
.IP \[bu] 2
ctr
.IP \[bu] 2
ofb
.IP \[bu] 2
cbc
.IP \[bu] 2
cfb
.IP \[bu] 2
ecb
.SS Misc
.IP \[bu] 2
null
.SS Complex Specifiers
.PP
Objects, when specified for creation by the TPM, have numerous
algorithms to populate in the public data.
Things like type, scheme and asymmetric details, key size, etc.
Below is the general format for specifying this data:
\f[C]<type>:<scheme>:<symmetric\-details>\f[]
.SS Type Specifiers
.PP
This portion of the complex algorithm specifier is required.
The remaining scheme and symmetric details will default based on the
type specified and the type of the object being created.
.IP \[bu] 2
aes \- Default AES: aes128
.IP \[bu] 2
aes128\f[C]<mode>\f[] \- 128 bit AES with optional mode
(\f[I]ctr\f[]|\f[I]ofb\f[]|\f[I]cbc\f[]|\f[I]cfb\f[]|\f[I]ecb\f[]).
If mode is not specified, defaults to \f[I]null\f[].
.IP \[bu] 2
aes192\f[C]<mode>\f[] \- Same as aes128\f[C]<mode>\f[], except for a 192
bit key size.
.IP \[bu] 2
aes256\f[C]<mode>\f[] \- Same as aes128\f[C]<mode>\f[], except for a 256
bit key size.
.IP \[bu] 2
ecc \- Elliptical Curve, defaults to ecc256.
.IP \[bu] 2
ecc192 \- 192 bit ECC
.IP \[bu] 2
ecc224 \- 224 bit ECC
.IP \[bu] 2
ecc256 \- 256 bit ECC
.IP \[bu] 2
ecc384 \- 384 bit ECC
.IP \[bu] 2
ecc521 \- 521 bit ECC
.IP \[bu] 2
rsa \- Default RSA: rsa2048
.IP \[bu] 2
rsa1024 \- RSA with 1024 bit keysize.
.IP \[bu] 2
rsa2048 \- RSA with 2048 bit keysize.
.IP \[bu] 2
rsa4096 \- RSA with 4096 bit keysize.
.SS Scheme Specifiers
.PP
Next, is an optional field, it can be skipped.
.PP
Schemes are usually \f[B]Signing Schemes\f[] or \f[B]Asymmetric
Encryption Schemes\f[].
Most signing schemes take a hash algorithm directly following the
signing scheme.
If the hash algorithm is missing, it defaults to \f[I]sha256\f[].
Some take no arguments, and some take multiple arguments.
.SS Hash Optional Scheme Specifiers
.PP
These scheme specifiers are followed by a dash and a valid hash
algorithm, For example: \f[C]oaep\-sha256\f[].
.IP \[bu] 2
oaep
.IP \[bu] 2
ecdh
.IP \[bu] 2
rsassa
.IP \[bu] 2
rsapss
.IP \[bu] 2
ecdsa
.IP \[bu] 2
ecschnorr
.SS Multiple Option Scheme Specifiers
.PP
This scheme specifier is followed by a count (max size UINT16) then
followed by a dash(\-) and a valid hash algorithm.
* ecdaa For example, ecdaa4\-sha256.
If no count is specified, it defaults to 4.
.SS No Option Scheme Specifiers
.PP
This scheme specifier takes NO arguments.
* rsaes
.SS Symmetric Details Specifiers
.PP
This field is optional, and defaults based on the \f[I]type\f[] of
object being created and it\[aq]s attributes.
Generally, any valid \f[B]Symmetric\f[] specifier from the \f[B]Type
Specifiers\f[] list should work.
If not specified, an asymmetric objects symmetric details defaults to
\f[I]aes128cfb\f[].
.SS Examples
.SS Create an rsa2048 key with an rsaes asymmetric encryption scheme
.PP
\f[C]tpm2_create\ \-C\ parent.ctx\ \-G\ rsa2048:rsaes\ \-u\ key.pub\ \-r\ key.priv\f[]
.SS Create an ecc256 key with an ecdaa signing scheme with a count of 4
and sha384 hash
.PP
\f[C]/tpm2_create\ \-C\ parent.ctx\ \-G\ ecc256:ecdaa4\-sha384\ \-u\ key.pub\ \-r\ key.priv\f[]
cryptographic algorithms \f[I]ALGORITHM\f[].
.SH Object Attributes
.PP
Object Attributes are used to control various properties of created
objects.
When specified as an option, either the raw bitfield mask or
"nice\-names" may be used.
The values can be found in Table 31 Part 2 of the TPM2.0 specification,
which can be found here:
.PP
<https://trustedcomputinggroup.org/wp-content/uploads/TPM-Rev-2.0-Part-2-Structures-01.38.pdf>
.PP
Nice names are calculated by taking the name field of table 31 and
removing the prefix \f[B]TPMA_OBJECT_\f[] and lowercasing the result.
Thus, \f[B]TPMA_OBJECT_FIXEDTPM\f[] becomes fixedtpm.
Nice names can be joined using the bitwise or "|" symbol.
.PP
For instance, to set The fields \f[B]TPMA_OBJECT_FIXEDTPM\f[],
\f[B]TPMA_OBJECT_NODA\f[], and \f[B]TPMA_OBJECT_SIGN_ENCRYPT\f[], the
argument would be:
.PP
\f[B]fixedtpm|noda|sign\f[] specifying the object attributes
\f[I]ATTRIBUTES\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 Setup
.PP
In order to create an object, we must first create a primary key as
it\[aq]s parent.
.IP
.nf
\f[C]
tpm2_createprimary\ \-c\ primary.ctx
\f[]
.fi
.SS Create an Object
.PP
This will create an object using all the default values and store the
TPM sealed private and public portions to the paths specified via \-u
and \-r respectively.
The tool defaults to an RSA key.
.IP
.nf
\f[C]
tpm2_create\ \-C\ primary.ctx\ \-u\ obj.pub\ \-r\ obj.priv
\f[]
.fi
.SS Seal Data to the TPM
.PP
Outside of key objects, the TPM allows for small amounts of user
specified data to be sealed to the TPM.
.IP
.nf
\f[C]
echo\ "my\ sealed\ data"\ >\ seal.dat
tpm2_create\ \-C\ primary.ctx\ \-i\ seal.dat\ \-u\ obj.pub\ \-r\ obj.priv
\f[]
.fi
.SS Create an EC Key Object and Load it to the TPM
.PP
Normally, when creating an object, only the public and private portions
of the object are returned and the caller needs to use tpm2_load(1) to
load those public and private portions to the TPM before being able to
use the object.
However, this can be accomplished within this command as well, when
supported by the TPM.
You can verify your TPM supports this feature by checking that
tpm2_getcap(1) commands returns TPM2_CC_CreateLoaded in the command set.
If your TPM does not support TPM2_CC_CreateLoaded an unsuported command
code error will be returned.
If it\[aq]s not supported one must use tpm2_load(1).
See that manpage for details on its usage.
.IP
.nf
\f[C]
tpm2_create\ \-C\ primary.ctx\ \-G\ ecc\ \-u\ obj.pub\ \-r\ obj.priv\ \-c\ ecc.ctx
\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)