tss2_gettpmblobs(1)

πŸ’– NAME πŸ’–

Okay bestie, welcome to tss2_gettpmblobs(1) from the General Commands Manual πŸ’… This is the little command that grabs the public and private blobs of an object for you, so a low-level API can load them later. It also hands over the policy attached to those blobs in JSON. Iconic behavior, honestly ✨


✨ SYNOPSIS ✨

tss2_gettpmblobs [OPTIONS]

πŸ¦‹ SEE ALSO πŸ¦‹

  • fapi-config(5) β€” use this to adjust Fapi parameters like the cryptographic profile and TCTI, or the 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 🌸

tss2_gettpmblobs(1) literally returns the public and private blobs of an object, such that they could be loaded by a low-level API (e.g. ESAPI). It also returns the policy associated with these blobs in JSON format. No cap, that’s the whole vibe πŸ’–


πŸ’… OPTIONS πŸ’…

These are the available options, bestie:

  • -f, --force β€” Force overwriting the output file. Use it when you’re feeling brave πŸ’€
  • -p, --path=STRING β€” The path of the object for which the blobs will be returned.
  • -u, --tpm2bPublic=FILENAME or - (for stdout) β€” The returned public area of the object as a marshalled TPM2B_PUBLIC. Optional parameter πŸ‘‘
  • -r, --tpm2bPrivate=FILENAME or - (for stdout) β€” The returned private area of the object as a marshalled TPM2B_PRIVATE. Optional parameter πŸŽ€
  • -l, --policy=FILENAME or - (for stdout) β€” The returned policy associated with the object, encoded in JSON. Optional parameter 🌈

πŸŽ€ COMMON OPTIONS πŸŽ€

This collection of options are common to all tss2 programs and provide information that many users may expect. Group-chat essentials, fr fr 🫢

  • -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 is 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. Do not skip this part, bestie 😭

  • -v, --version β€” Display version information for this tool, supported tctis and exit. Short, sweet, slays ✨

πŸ“ EXAMPLE πŸ“

tss2_gettpmblobs --path=HS/SRK/myRSACrypt --tpm2bPublic=tpm2bPublic.file --tpm2bPrivate=tpm2bPrivate.file --policy=policy.file

⭐ RETURNS ⭐

0 on success or 1 on failure. Simple as that πŸ’–


πŸ’€ BUGS πŸ’€

Github Issues iykyk πŸ™ˆ


🫢 HELP 🫢

See the Mailing List πŸ’Œ


🌈 License 🌈

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


That’s the whole tss2_gettpmblobs(1) situation, bestie β€” brought to you by tpm2-tools, dated APRIL 2019 🌸🫢

πŸ“¦ where this page comes from