tss2_createseal(1)

🌸 NAME 🌸

Okay bestie, this is tss2_createseal(1) from the General Commands Manual — the whole name section is literally just the command name, no extra subtitle, and honestly? Iconic minimalism. 💅

✨ SYNOPSIS ✨

tss2_createseal [OPTIONS]

🦋 SEE ALSO 🦋

• fapi-config(5) — use this to adjust Fapi parameters like the used cryptographic profile and TCTI or directories for the Fapi metadata storages.
• fapi-profile(5) — use this to determine the cryptographic algorithms and parameters for all keys and operations of a specific TPM interaction like the name hash algorithm, the asymmetric signature algorithm, scheme and parameters and PCR bank selection.

💅 DESCRIPTION 💅

So tss2_createseal(1) creates a sealed object and stores it in the FAPI metadata store. That's the main character move. ✨

If no data is provided (i.e. a NULL-pointer) then the TPM generates random data and fills the sealed object. TPM signing schemes are used as specified in the cryptographic profile (cf., fapi-profile(5)). No cap, that's the whole vibe.

🎀 OPTIONS 🎀

These are the available options:

• -p, --path=STRING — The path to the new key.
• -t, --type=STRING — Identifies the intended usage. Optional parameter. Types may be any comma-separated combination of:
  • "exportable": Clears the fixedTPM and fixedParent attributes of a key or sealed object.
  • "noda": Sets the noda attribute of a key or NV index.
  • "system": Stores the data blobs and metadata for a created key or seal in the system-wide directory instead of user's personal directory.
  • A hexadecimal number (e.g. "0x81000001"): Marks a key object to be made persistent and sets the persistent object handle to this value.
• -P, --policyPath=STRING — Identifies the policy to be associated with the new key. Optional parameter. If omitted then no policy will be associated with the key.

A policyPath is composed of two elements, separated by “/”. A policyPath starts with “/policy”. The second path element identifies the policy or policy template using a meaningful name.

• -a, --authValue=STRING — The new UTF-8 password. Optional parameter. If it is neglected then the user is queried interactively for a password. To set no password, this option should be used with the empty string (““). The maximum password size is determined by the digest size of the chosen name hash algorithm in the cryptographic profile (cf., fapi-profile(5)). For example, choosing SHA256 as hash algorithm, allows passwords of a maximum size of 32 characters.
• -i, --data=FILENAME or - (for stdin) — The data to be sealed by the TPM. Optional parameter. Must not be used together with --size.
• -s, --size=INTEGER — Determines the number of random bytes the TPM should generate and seal. Optional parameter. Must not be “0”. Must not be used together with --data.

🌈 COMMON OPTIONS 🌈

This collection of options are common to all tss2 programs and provide information that many users may expect.

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

⭐ EXAMPLE ⭐

Create a key with password “abc” and read sealing data from file.

tss2_createseal --path=HS/SRK/mySealKey --type="noDa" --authValue=abc --data=data.file

🍓 RETURNS 🍓

0 on success or 1 on failure. That's it, bestie — binary mood. 💀

💀 BUGS 💀

Github Issues

🫶 HELP 🫶

See the Mailing List

📜 License 📜

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

---

That's the whole page, bestie! 💖 Source/version: tpm2-tools; date: APRIL 2019; and yes, we're still living in tss2_createseal(1) ✨🦋