tpm_nvwrite(8)

πŸ“¦
version 1.3.9.2 Β· 2 versions
  • 1.3.9.2 Β· debian bookworm, debian trixie, epel 10, epel 9, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 1.3.9.1 Β· ubuntu jammy
, in debian bookworm, debian trixie, epel 10, epel 9, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– tpm_nvwrite β€” the NVRAM glow-up page πŸ’–

okay bestie, welcome to the tpm_nvwrite(8) manual page, section 8, TPM Management core. this is the one that puts your bytes into an NVRAM area, and honestly? it ate. let's get into it 🫢


🌸 NAME 🌸

tpm_nvwrite β€” no cap, that's literally the whole name, she's iconic like that ✨


πŸŽ€ SYNOPSIS πŸŽ€

tpm_nvwrite [OPTIONS]

just the command and your options, that's the whole vibe πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea: tpm_nvwrite writes data to an NVRAM area. that's the mission, that's the moment.

to make it happen you have to hand her two things β€” the index of the NVRAM area and the data you want written into that NVRAM area. no index, no data, no slay. periodt.

optionally, you can also give her an offset into the NVRAM area β€” that's where the writing starts, so you can slide in at whatever position you want. and similarly, you can tell her the number of bytes to write into the NVRAM area. very "I know exactly how much I'm giving you" energy.

heads up bestie: some NVRAM areas only allow write sizes of zero, i.e., NVRAM area index 0. so don't come for her when a size of zero is the whole assignment πŸ’€

and if the NVRAM area has permission bits set that require owner or NVRAM area authentication, then you must provide the password via the password option. no password, no entry. it's giving bouncer at the club πŸ™ˆ

the following options are supported β€” yes, all of them, I'm not skipping a single one, we're thorough in this group chat:

  • -h, --help β€” display command usage info. the "what do I do" button πŸŽ€
  • -v, --version β€” display command version info. the "who even are you" button ⭐
  • -l, --log [none|error|info|debug] β€” set the logging level. pick your level of yapping: none, error, info, or debug 🌈
  • -u, --unicode β€” use TSS UNICODE encoding for passwords, so it complies with applications that use TSS popup boxes πŸ”₯
  • -z, --well-known β€” use a secret of all zeros (20 bytes of zeros) as either the NVRAM area or owner secret. the "it's giving nothing but zeros, and that's the point" option πŸ’œ
  • -p, --password β€” depending on what type of authentication the NVRAM area requires, this must either be the NVRAM area password or the owner password. a password may be directly provided, for example by using '--password=password' or -ppassword. if no password is provided, then the program will prompt the user for the password. she'll ask, she's polite like that πŸ’…
  • -i, --index (optional parameter) β€” the index of the NVRAM area. the parameter may either be a decimal number or a hexadecimal number starting with '0x' πŸ”’
  • -s, --size β€” the number of bytes to write to the NVRAM area. this parameter may be used for truncating the data that are, for example, read from a file. the parameter may either be a decimal number or a hexadecimal number starting with '0x' βœ‚οΈ
  • -n, --offset (optional parameter) β€” the offset into the NVRAM area where to start writing. the parameter may either be a decimal number or a hexadecimal number starting with '0x' πŸ“
  • -f, --filename (optional parameter) β€” the name of a file from which to read data and copy them into the NVRAM area. file girlies rise πŸ“
  • -d, --data (optional parameter) β€” the data to write into the NVRAM area, passed in the command line. for when you just wanna say it out loud πŸ—£οΈ
  • -m, --fill-value (optional parameter) β€” the byte to fill the NVRAM area with. one single byte, doing the absolute most ✨

πŸ‘‘ SEE ALSO πŸ‘‘

go read her sisters, they're all main characters too:


πŸ’€ REPORTING BUGS πŸ’€

found a bug? not me, not you, but like… if you did β€” report bugs to <trousers-users@lists.sourceforge.net> πŸ“¬


and that's the page, bestie πŸ’– this was TPM Management, dated 2011-07-11, and yeah she's been serving since day one. mwah, go write some NVRAM 🧚πŸ’