tpm2_ecdhkeygen(1)

๐Ÿ’… tpm2_ecdhkeygen(1) ๐Ÿ’…

okay so this is from the General Commands Manual bestie, and it's about tpm2_ecdhkeygen(1) โ€” the little icon that makes an ephemeral key and then uses it to generate the shared secret value using the parameters from an ECC public key. periodt. ๐ŸŽ€


โœจ NAME โœจ

tpm2_ecdhkeygen(1) โ€” Creates an ephemeral key and uses it to generate the shared secret value using the parameters from a ECC public key. ๐Ÿฆ‹


๐ŸŒธ SYNOPSIS ๐ŸŒธ

tpm2_ecdhkeygen [OPTIONS]

๐Ÿฆ‹ DESCRIPTION ๐Ÿฆ‹

So tpm2_ecdhkeygen(1) โ€” and yes I'm saying it again because the page says it again โ€” Creates an ephemeral key and uses it to generate the shared secret value using the parameters from a ECC public key. it's giving one-job icon and honestly? she ate. ๐Ÿ’…


๐Ÿ’– OPTIONS ๐Ÿ’–

  • -c, --context=FILE โ€” the context object pointing to your ECC public key. it can be either a file or a handle number. go read the section called "Context Object Format" if you need the deets, iykyk.
  • -u, --public=FILE โ€” output ECC point Q. that's the output, bestie, that's where Q goes. โœจ
  • -o, --output=FILE โ€” specify file path to save the calculated ecdh secret or Z point. ๐ŸŒธ
  • --cphash=FILE โ€” 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. no cap, it just hands you the hash and dips. ๐Ÿ’€

๐Ÿ“š References ๐Ÿ“š

๐Ÿ”ฎ Algorithm Specifiers ๐Ÿ”ฎ

Options 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. like, the TPM is the bouncer and she has a list. ๐Ÿซถ

๐Ÿงš Simple specifiers ๐Ÿงš

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. ๐Ÿ‘‡

๐Ÿ”‘ Asymmetric

  • rsa
  • ecc

๐ŸŒˆ Symmetric

  • aes
  • camellia
  • sm4

๐Ÿ“ Hashing Algorithms

  • sha1
  • sha256
  • sha384
  • sha512
  • sm3_256
  • sha3_256
  • sha3_384
  • sha3_512

๐ŸŽ€ Keyed Hash

  • hmac
  • xor

โœ๏ธ Signing Schemes

  • rsassa
  • rsapss
  • ecdsa
  • ecdaa
  • ecschnorr
  • sm2

๐Ÿ” Asymmetric Encryption Schemes

  • oaep
  • rsaes
  • ecdh

๐Ÿ” Modes

  • ctr
  • ofb
  • cbc
  • cfb
  • ecb

๐ŸŒ€ Misc

  • null

๐ŸŒŸ Complex Specifiers ๐ŸŒŸ

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: <type>:<scheme>:<symmetric-details> โญ

๐Ÿฆ‹ Type Specifiers ๐Ÿฆ‹

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.

  • aes โ€” Default AES: aes128
  • aes128<mode> โ€” 128 bit AES with optional mode (ctr|ofb|cbc|cfb|ecb). If mode is not specified, defaults to null.
  • aes192<mode> โ€” Same as aes128<mode>, except for a 192 bit key size.
  • aes256<mode> โ€” Same as aes128<mode>, except for a 256 bit key size.
  • sm4 โ€” Default SM4: sm4128
  • sm4128 or sm4_128 <mode> โ€” 128 bit SM4 with optional mode (ctr|ofb|cbc|cfb|ecb). If mode is not specified, defaults to null.
  • ecc โ€” Elliptical Curve, defaults to ecc256.
  • ecc192 or ecc_nist_p192 โ€” 192 bit ECC NIST curve
  • ecc224 or ecc_nist_p224 โ€” 224 bit ECC NIST curve
  • ecc256 or ecc_nist_p256 โ€” 256 bit ECC NIST curve
  • ecc384 or ecc_nist_p384 โ€” 384 bit ECC NIST curve
  • ecc521 or ecc_nist_p521 โ€” 521 bit ECC NIST curve
  • ecc_sm2 or ecc_sm2_p256 โ€” 256 bit SM2 curve
  • rsa โ€” Default RSA: rsa2048
  • rsa1024 โ€” RSA with 1024 bit keysize.
  • rsa2048 โ€” RSA with 2048 bit keysize.
  • rsa3072 โ€” RSA with 3072 bit keysize.
  • rsa4096 โ€” RSA with 4096 bit keysize.

๐ŸŽฏ Scheme Specifiers ๐ŸŽฏ

Next, is an optional field, it can be skipped. (skip it, live your life ๐Ÿ’œ)

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 Specifiers ๐Ÿงธ

These scheme specifiers are followed by a dash and a valid hash algorithm, For example: oaep-sha256.

  • oaep
  • ecdh
  • rsassa
  • rsapss
  • ecdsa
  • ecschnorr
  • sm2

๐Ÿฌ Multiple Option Scheme Specifiers ๐Ÿฌ

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.

๐ŸงŠ No Option Scheme Specifiers ๐ŸงŠ

This scheme specifier takes NO arguments. rsaes

๐Ÿ’Ž Symmetric Details Specifiers ๐Ÿ’Ž

This 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.


๐Ÿ’ Examples ๐Ÿ’

Create an rsa2048 key with an rsaes asymmetric encryption scheme

tpm2_create -C parent.ctx -G rsa2048:rsaes -u key.pub -r key.priv

Create 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.

(yes the trailing cryptographic algorithms ALGORITHM. is really in there. we don't ask questions, we just copy the icon faithfully ๐Ÿ˜ญ)


๐ŸŒผ COMMON OPTIONS ๐ŸŒผ

This collection of options are common to many programs and provide information that many users may expect. the group-chat classics, basically. ๐Ÿซถ

  • -h, --help=[man|no-man] โ€” 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.

To successfully use the manpages feature requires the manpages to be installed or on MANPATH, See man(1) for more details.

  • -v, --version โ€” Display version information for this tool, supported tctis and exit.
  • -V, --verbose โ€” Increase the information that the tool prints to the console during its execution. When using this option the file and line number are printed.
  • -Q, --quiet โ€” Silence normal tool output to stdout.
  • -Z, --enable-errata โ€” 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.
  • -z, --pwd-session โ€” Use password session instead of a HMAC session for authentication. A clear text password is passed to the TPM to authorize the action. This option can be used to avoid problems when unsalted sessions are used in OpenSSL FIPS mode. If auth values are used a salted session should be used for authentication.
  • -R, --autoflush โ€” Enable autoflush for transient objects created by the command. If a parent object is loaded from a context file also the transient parent object will be flushed. Autoflush can also be activated if the environment variable TPM2TOOLS_AUTOFLUSH is set to yes or true. information many users may expect. ๐Ÿ’€
and yeah that last fragment "information many users may expect." is verbatim from the page. she's a little unhinged but she's our icon. ๐ŸŽ€

๐Ÿ“ก TCTI Configuration ๐Ÿ“ก

The TCTI or "Transmission Interface" is the communication mechanism with the TPM. TCTIs can be changed for communication with TPMs across different mediums. it's giving switchboard energy. ๐Ÿ”Œ

To control the TCTI, the tools respect:

  1. The command line option -T or --tcti
  2. The environment variable: TPM2TOOLS_TCTI.
Note: The command line option always overrides the environment variable. no exceptions bestie. ๐Ÿ’…

The current known TCTIs are:

  • tabrmd โ€” The resource manager, called tabrmd. Note that tabrmd and abrmd as a tcti name are synonymous.
  • mssim โ€” Typically used for communicating to the TPM software simulator.
  • device โ€” Used when talking directly to a TPM device file.
  • 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 ANY options and MUST BE presented as the exact text of "none". (exact text, fr fr, no lowercase games)

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 Defaults ๐Ÿงš

When 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 TCTIs ๐ŸŒˆ

Any 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 OPTIONS ๐Ÿ”ง

This collection of options are used to configure the various known TCTI modules available:

  • device โ€” For the device TCTI, the TPM character device file for use by the device TCTI can be specified. The default is /dev/tpm0.

Example: -T device:/dev/tpm0 or export TPM2TOOLS_TCTI="device:/dev/tpm0"

  • mssim โ€” 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.

Example: -T mssim:host=localhost,port=2321 or export TPM2TOOLS_TCTI="mssim:host=localhost,port=2321"

  • abrmd โ€” For the abrmd TCTI, the configuration string format is a series of simple key value pairs separated by a , character. Each key and value string are separated by a = character.
    • TCTI abrmd supports two keys:
      1. bus_name : The name of the tabrmd service on the bus (a string).
      2. bus_type : The type of the dbus instance (a string) limited to session and system.

Specify the tabrmd tcti name and a config string of bus_name=com.example.FooBar:

\--tcti=tabrmd:bus_name=com.example.FooBar

Specify the default (abrmd) tcti and a config string of bus_type=session:

\--tcti:bus_type=session
NOTE: abrmd and tabrmd are synonymous. the various known TCTI modules. ๐Ÿ’ซ

๐Ÿ”ฅ EXAMPLES ๐Ÿ”ฅ

tpm2_createprimary -C o -c prim.ctx -Q

tpm2_create -C prim.ctx -c key.ctx -u key.pub -r key.priv -G ecc256:ecdaa

tpm2_ecdhkeygen -u ecdh.pub -o ecdh.priv -c key.ctx

look at her go. three lines, zero notes, absolute main character energy. ๐Ÿ‘‘

๐ŸŽ€ RETURNS ๐ŸŽ€

okay so like, bestie, this is the part where you find out if it worked ๐Ÿ’– Tools can return any of the following codes:

  • 0 โ€” Success. slay ๐Ÿ’… literally the dream, everything went off without a hitch.
  • 1 โ€” General non-specific error. not giving anything specific, just vibes of failure ๐Ÿ˜ญ
  • 2 โ€” Options handling error. you fumbled the flags, bestie โ€” check your arguments.
  • 3 โ€” Authentication error. the auth didn't auth ๐Ÿ™ˆ
  • 4 โ€” TCTI related error. something's up with the TCTI layer, iykyk.
  • 5 โ€” Non supported scheme. Applicable to tpm2_testparams. not me trying a scheme that isn't supported ๐Ÿ’€

๐Ÿ› BUGS ๐Ÿ›

Github Issues โ€” that's literally where the bugs live, go report 'em there ๐Ÿซถ

๐Ÿ†˜ HELP ๐Ÿ†˜

See the Mailing List โ€” the girlies on the list have answers, fr fr ๐ŸŒธ

๐Ÿ“œ License ๐Ÿ“œ

This work is licensed under the Creative Commons Attribution 4.0 International License (CC BY 4.0). iconic, legal, and free โ€” periodt โœจ


๐Ÿ’– and that's the whole page, bestie! ๐Ÿ’–

this masterpiece of a manual page comes to you from tpm2-tools, and you're reading tpm2_ecdhkeygen(1) โ€” go forth and generate those ECDH keys, you absolute main character ๐Ÿ‘‘๐Ÿฆ‹๐Ÿ’œ

๐Ÿ“ฆ where this page comes from