CERTIFYCREATION(1)

πŸ“¦
version 1045 Β· 3 versions
, in debian bookworm, ubuntu jammy, ubuntu noble, ubuntu questing

πŸ’– CERTIFYCREATION(1) β€” like, the manual page, but make it make sense πŸ’–

okay bestie, welcome to certifycreation, a User Command. this whole thing lives under the manual name certifycreation, and honestly? she's a lil chaotic but we love her. grab a boba, we're doing this together. πŸ§‹βœ¨


🌸 NAME 🌸

certifycreation β€” she runs TPM2_CertifyCreation. that's the whole vibe. no cap. πŸ’…


✨ DESCRIPTION ✨

okay so first thing's first, and this is important, bestie:

--version-string=v1045 is not a valid option. not valid. not it. 🚫

then we get:

certify

Runs TPM2_CertifyCreation πŸ’«

here's the actual lineup of what she takes, and yes, every single one matters:

  • -ho β€” object handle πŸ‘‘
  • -hk β€” certifying key handle πŸ”‘

and then the optional besties in brackets:

  • [-pwdk password for key (default empty)] β€” password for the key, and if you don't hand one over, it's just empty, no biggie
  • [-halg (sha1, sha256, sha384) (default sha256)] β€” pick your hash algo from sha1, sha256, or sha384; default is sha256 ⭐
  • [-salg signature algorithm (rsa, ecc) (default rsa)] β€” signature algorithm, either rsa or ecc, default rsa
  • [-qd qualifying data file name] β€” the qualifying data file name
  • -tk input ticket file name β€” input ticket file name (this one's not optional, she NEEDS it)
  • -ch input creation hash file name β€” input creation hash file name (also required, periodt)
  • [-os signature file name] (default do not save) β€” signature file name, but default is do not save πŸ™ˆ
  • [-oa attestation output file name (default do not save)] β€” attestation output file name, default is also do not save πŸ™ˆ

then:

  • -se[0-2] β€” session handle / attributes (default PWAP)
    • 01 continue

and THEN, because the universe has a sense of humor, we get this again:

--version is not a valid option. nope. not valid. πŸ’€

certify

Runs TPM2_CertifyCreation πŸ”₯

  • -ho β€” object handle πŸ‘‘
  • -hk β€” certifying key handle πŸ”‘

optionals, take two, same energy:

  • [-pwdk password for key (default empty)] β€” password for the key, default empty
  • [-halg (sha1, sha256, sha384) (default sha256)] β€” hash algorithm, sha1 / sha256 / sha384, default sha256
  • [-salg signature algorithm (rsa, ecc) (default rsa)] β€” signature algorithm, rsa / ecc, default rsa
  • [-qd qualifying data file name] β€” qualifying data file name
  • -tk input ticket file name β€” input ticket file name
  • -ch input creation hash file name β€” input creation hash file name
  • [-os signature file name] (default do not save) β€” signature file name, default do not save
  • [-oa attestation output file name (default do not save)] β€” attestation output file name, default do not save

and again, one more time:

  • -se[0-2] β€” session handle / attributes (default PWAP)
    • 01 continue

yeah. she said it twice. iconic behavior honestly. πŸ’…βœ¨


πŸ¦‹ SEE ALSO πŸ¦‹

the full documentation for certifycreation is maintained as a Texinfo manual. if the info and certifycreation programs are properly installed at your site, the command

info certifycreation

should give you access to the complete manual. πŸ“–πŸŒΈ


and that's the whole page bestie, you ate that 🫢

certifycreation β€” July 2017 β€” CERTIFYCREATION(1) πŸ’– that's the sign-off, mwah, go certify some creations πŸ‘‘βœ¨πŸŽ€

πŸ“¦ where this page comes from