tpm2_changeeps(1)

hii bestie 💖 welcome to the tpm2_changeeps(1) page from the tpm2-tools manual — the one that's all about swapping out your endorsement primary seed. it's giving "fresh start" energy and honestly? we're obsessed. periodt. ✨

🎀 NAME 🎀

tpm2_changeeps(1) — replaces the active endorsement primary seed with a shiny new one generated off the TPM2 RNG. that's the whole vibe. 💅

✨ SYNOPSIS ✨

tpm2_changeeps [OPTIONS]

💖 DESCRIPTION 💖

okay so bestie, here's the tea ☕ — tpm2_changeeps(1) swaps your active endorsement primary seed for a brand new one generated off the TPM2 RNG. the way that this is a big deal: the Transient and Persistent objects hanging out under the endorsement hierarchy are lost. like gone gone. 😭 no cap, they do not survive this.

also important: this command requires platform auth. don't forget it. 🔑

🔥 OPTIONS 🔥

• -p, --auth=AUTH — specifies the AUTH for the platform hierarchy. this is your platform auth ticket, bestie 🎟️
• --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, unless rphash is also required. iykyk 👀
• --rphash=FILE — file path to record the hash of the response parameters. this is commonly termed as rpHash. matching set with cphash fr fr 💫
• -S, --session=FILE: — the session created using tpm2_startauthsession. this can be used to specify an auxiliary session for auditing and/or encryption/decryption of the parameters. very main character energy 🌟

---

🫶 References 🫶

💖 Authorization Formatting 💖

authorization for use of an object in TPM2.0 can come in 3 different forms, bestie:

1. Password
2. HMAC
3. Sessions

NOTE: "Authorizations default to the EMPTY PASSWORD when not specified". yes that's the whole point, don't come for me 🙈

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)). slay for secure defaults 🔐

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 its absence (raw string without prefix) is not interpreted, and is directly used for authorization. simple as that ✨

Examples:

foobar
str:foobar

Hex-string

a hex-string password, specified by prefix hex: is converted from a hexadecimal form into a byte array form — thus allowing passwords with non-printable and/or terminal un-friendly characters. no more keyboard-mashing mysteries 🦋

Example:

hex:1122334455667788

File

a file based password, specified with the 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. protect your secrets bestie 💜

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. okay so it's giving modular ✨

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

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.

---

🌈 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 versatile 💫

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 debate 👑

the current known TCTIs are:

• tabrmd — the resource manager, called tabrmd. note that tabrmd and abrmd as a tcti name are synonymous. same vibe, different name 💅
• mssim — typically used for communicating to the TPM software simulator. simulator girlies rise 🌸
• device — used when talking directly to a TPM device file. old school, we respect it 🫶
• none — do not initialize 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". read that again — exact text bestie, no extra characters 😤

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. mystery solved 🔎

🦋 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. bring your own TCTI, we love a custom moment 🎀

---

🎀 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 defaults 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 🌟

Change the endorsement primary seed where the platform auth is NULL.

tpm2_changeeps

that's it. that's the example. iconic minimalism 💅

👑 Returns 👑

tools can return any of the following codes:

• 0 — Success. we love a win 🎉
• 1 — General non-specific error. vague but okay 😭
• 2 — Options handling error. check your flags bestie 🚩
• 3 — Authentication error. wrong key energy 🔐
• 4 — TCTI related error. communication breakdown 💀
• 5 — Non supported scheme. applicable to tpm2_testparams. not every scheme is invited to the party 🙈

🍓 Limitations 🍓

it expects a session to be already established via tpm2_startauthsession(1) and requires one of the following:

• direct device access
• extended session support with tpm2-abrmd.

without it, most resource managers will not save session state between command invocations. so plan ahead, bestie 🧚

💀 BUGS 💀

Github Issues. the classic. found a bug? the github is right there 🫶

🌈 HELP 🌈

See the Mailing List. the group chat of the tpm2 world ✨

💜 License 💜

this work is licensed under the Creative Commons Attribution 4.0 International License (CC BY 4.0).

---

~ fin ~ 💖 brought to you by the tpm2-tools gang, dated whenever this manual page was last touched — no cap, slay, and happy seed-swapping bestie 🎀✨💅