|
NAMEtpm2_geteccparameters(1) - Retrieves the parameters of an ECC curve identified by its TCG-assigned curveID.SYNOPSIStpm2_geteccparameters [OPTIONS]DESCRIPTIONtpm2_geteccparameters(1) - Retrieves the parameters of an ECC curve identified by its TCG-assigned curveID.OPTIONS
Specify the ECC curve. Example ecc521.
Specify the file path to save the ECC parameters. ReferencesAlgorithm SpecifiersOptions that take algorithms support “nice-names”.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. Simple specifiersThese 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”.Asymmetric
Symmetric
Hashing Algorithms
Keyed Hash
Signing Schemes
Asymmetric Encryption Schemes
Modes
Misc
Complex SpecifiersObjects, 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: <type>:<scheme>:<symmetric-details>Type SpecifiersThis 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.
Scheme SpecifiersNext, is an optional field, it can be skipped.Schemes are usually Signing Schemes or Asymmetric Encryption Schemes. Most signing schemes take a hash algorithm directly following the signing scheme. If the hash algorithm is missing, it defaults to sha256. Some take no arguments, and some take multiple arguments. Hash Optional Scheme SpecifiersThese scheme specifiers are followed by a dash and a valid hash algorithm, For example: oaep-sha256.
Multiple Option Scheme SpecifiersThis 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.No Option Scheme SpecifiersThis scheme specifier takes NO arguments. * rsaesSymmetric Details SpecifiersThis field is optional, and defaults based on the type of object being created and it’s attributes. Generally, any valid Symmetric specifier from the Type Specifiers list should work. If not specified, an asymmetric objects symmetric details defaults to aes128cfb.ExamplesCreate an rsa2048 key with an rsaes asymmetric encryption schemetpm2_create -C parent.ctx -G rsa2048:rsaes -u key.pub -r key.privCreate an ecc256 key with an ecdaa signing scheme with a count of 4 and sha384 hash/tpm2_create -C parent.ctx -G ecc256:ecdaa4-sha384 -u key.pub -r key.priv cryptographic algorithms ALGORITHM.COMMON OPTIONSThis collection of options are common to many programs and provide information that many users may expect.
To successfully use the manpages feature requires the manpages to be installed or on MANPATH, See man(1) for more details.
TCTI ConfigurationThe TCTI or “Transmission Interface” is the communication mechanism with the TPM. TCTIs can be changed for communication with TPMs across different mediums.To control the TCTI, the tools respect:
Note: The command line option always overrides the environment variable. The current known TCTIs are:
The arguments to either the command line option or the environment variable are in the form: <tcti-name>:<tcti-option-config> Specifying an empty string for either the <tcti-name> or <tcti-option-config> results in the default being used for that portion respectively. TCTI DefaultsWhen a TCTI is not specified, the default TCTI is searched for using dlopen(3) semantics. The tools will search for tabrmd, device and mssim TCTIs IN THAT ORDER and USE THE FIRST ONE FOUND. You can query what TCTI will be chosen as the default by using the -v option to print the version information. The “default-tcti” key-value pair will indicate which of the aforementioned TCTIs is the default.Custom TCTIsAny TCTI that implements the dynamic TCTI interface can be loaded. The tools internally use dlopen(3), and the raw tcti-name value is used for the lookup. Thus, this could be a path to the shared library, or a library name as understood by dlopen(3) semantics.TCTI OPTIONSThis collection of options are used to configure the various known TCTI modules available:
Example: -T device:/dev/tpm0 or export TPM2TOOLS_TCTI=“device:/dev/tpm0”
Example: -T mssim:host=localhost,port=2321 or export TPM2TOOLS_TCTI=“mssim:host=localhost,port=2321”
Specify the tabrmd tcti name and a config string of bus_name=com.example.FooBar:
Specify the default (abrmd) tcti and a config string of bus_type=session:
NOTE: abrmd and tabrmd are synonymous. the various known TCTI modules. EXAMPLES
ReturnsTools can return any of the following codes:
BUGSGithub Issues (https://github.com/tpm2-software/tpm2-tools/issues)HELPSee the Mailing List (https://lists.01.org/mailman/listinfo/tpm2)
Visit the GSP FreeBSD Man Page Interface. |