tpm2_clear(1)

📦
version 5.8 · 10 versions
, in arch rolling

✨ tpm2_clear(1) ✨

okay bestie, buckle up — this is tpm2_clear from the General Commands Manual, and it's lowkey one of those pages where the vibe is "one command, forty pages of shared boilerplate". We stan anyway. 💅

💖 NAME 💖

tpm2_clear(1) — Clears lockout, endorsement and owner hierarchy authorization values and other TPM data.

🦋 SYNOPSIS 🦋

tpm2_clear [OPTIONS] [ARGUMENT]

🌸 DESCRIPTION 🌸

tpm2_clear(1) — so what this does is send a clear command to the TPM to clear the 3 hierarchy authorization values. That's the whole personality. ✨

As an argument it takes the auth value for either the platform or lockout hierarchy.

If you want the deep lore — like, the actual details of the changes performed to the TPM — that lives in Part 3, "Commands", section of the TPM Library spec, at the URL below:

Please look for the version coresponding to your TPM support specification version, and the TPM2_Clear command. You can find out which spec version your TPM supports by issuing a tpm2_getcap properties-fixed on the TPM_PT_REVISION property. iykyk 🔍

NOTE: All objects created under the respective hierarchies are lost. 😭 Like, gone gone. Not "in the recycle bin" gone.

🎀 OPTIONS 🎀

  • -c, --auth-hierarchy=OBJECT — Specifies the hierarchy the tools should operate on. By default it operates on the lockout hierarchy.
NOTE: Operating on platform hierarchy require platform authentication. 🔐
  • --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. (So it's giving "look but don't touch" 💅)
  • ARGUMENT — the command line argument specifies the AUTH to be set for the object specified with -c.

📚 References 📚

🧚 Context Object Format 🧚

The type of a context object — whether it's a handle or a file name — is determined according to the following logic, in-order:

  • If the argument is a file path, then the file is loaded as a restored TPM transient object.
  • If the argument is a prefix match on one of:
    • owner: the owner hierarchy
    • platform: the platform hierarchy
    • endorsement: the endorsement hierarchy
    • lockout: the lockout control persistent object
  • If the argument argument can be loaded as a number it will be treat as a handle, e.g. 0x81010013 and used directly._OBJECT_.

🔑 Authorization Formatting 🔑

Authorization for use of an object in TPM2.0 can come in 3 different forms:

  1. Password
  2. HMAC
  3. Sessions
NOTE: "Authorizations default to the EMPTY PASSWORD when not specified".

For authentication with auth values, the tool commands implicitly generate an HMAC session. Thus passwords are not transmitted unencrypted. This does not apply to passwords defined for objects. In this case, an HMAC session should be used (see tpm2_startauthsession(1)).

🔒 Passwords 🔒

Passwords are interpreted in the following forms below using prefix identifiers.

Note: By default passwords are assumed to be in the string form when they do not have a prefix.

⭐ String ⭐

A string password, specified by prefix str: or it's absence (raw string without prefix) is not interpreted, and is directly used for authorization.

✨ Examples ✨

foobar
str:foobar

🌈 Hex-string 🌈

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.

🍓 Example 🍓

hex:1122334455667788

💜 File 💜

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. (fr fr, protect ur secrets 🫶)

🌸 Examples 🌸

# 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

🎀 Sessions 🎀

When using a policy session to authorize the use of an object, prefix the option argument with the session 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 Passwords section.

💫 Examples 💫

To use a session context file called session.ctx.

session:session.ctx

To use a session context file called session.ctx AND send the authvalue mypassword.

session:session.ctx+mypassword

To use a session context file called session.ctx AND send the HEX authvalue 0x11223344.

session:session.ctx+hex:11223344

🧬 PCR Authorizations 🧬

You can satisfy a PCR policy using the pcr: prefix and the PCR minilanguage. The PCR minilanguage is as follows:

<pcr-spec>=<raw-pcr-file>

The PCR spec is documented in in the section "PCR bank specifiers".

The raw-pcr-file is an optional argument that contains the output of the raw PCR contents as returned by tpm2_pcrread(1).

🦋 PCR bank specifiers 🦋

(this heading is literally just sitting here with no body under it in the original — iconic, no notes 💀)

🔥 Examples 🔥

To satisfy a PCR policy of sha256 on banks 0, 1, 2 and 3 use a specifier of:

pcr:sha256:0,1,2,3

specifying AUTH.

👑 COMMON OPTIONS 👑

This collection of options are common to many programs and provide information that many users may expect. (the shared group-chat, 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 is set to yes or true. information many users may expect.

🌐 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 the little messenger between u and ur TPM 💌)

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

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.

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 🎉

Set owner, endorsement and lockout authorizations to an empty value

tpm2_clear lockoutpasswd

Clear the authorization values on the platform hierarchy

tpm2_clear -c p

🍓 ok that's the first half, the rest of this page is coming at u in part 2 🫶

✨ RETURNS ✨

okay so bestie, here's the vibe check on what the tools can hand back to you — literally any of these codes are fair game:

  • 0 — Success. periodt. we ate and left no crumbs 💅
  • 1 — General non-specific error. it's giving "something's wrong but nobody knows what" 😭
  • 2 — Options handling error. your flags are not slaying, check them 🎀
  • 3 — Authentication error. nope, not you, wrong password energy 🙈
  • 4 — TCTI related error. the transport layer is lowkey going through it 💀
  • 5 — Non supported scheme. Applicable to tpm2_testparams. like, that scheme? not supported bestie 🦋

🐛 BUGS 🐛

Found a bug? Iconic of you. Go drop it at Github Issues — that's literally where they live 🫶

🌸 HELP 🌸

Need a hand? See the Mailing List — the girlies there know things, iykyk ✨

👑 License 👑

This work is licensed under the Creative Commons Attribution 4.0 International License (CC BY 4.0). fr fr, credit where credit is due 💜

and that's the whole page, bestie!! 🌈 this gorgeous little number comes to you straight from tpm2-tools, and the page itself is tpm2_clear(1) — go forth and clear those TPMs responsibly, mwah 💖🎀🦋

📦 where this page comes from