stpm-exfiltrate(1)
π stpm-exfiltrate β the manual page, bestie edition
okay so you found stpm-exfiltrate(1), the little tool from the simple-tpm-pk11 family, and you're like "what does this even do" β don't worry, I got you. sit down, hydrate, let's go. π«Ά
β¨ NAME β¨
stpm-exfiltrate β Extract key from TPM chip π
πΈ SYNOPSIS πΈ
stpm-exfiltrate [ -hOps ] -k key file
π DESCRIPTION π
stpm-exfiltrate extracts a key that is otherwise protected by the TPM chip. lowkey iconic of it, ngl.
BUT β and this is the plot twist β it only works if the key is "migratable" (meaning it was generated in software), and the TPM owner password is known. both. you need both. no cap.
which is exactly why you should generate keys in hardware (the default) with stpm-keygen and not use its -S option. fr fr. hardware keys = main character energy, software keys = the vibe check they fail. π
β¨ OPTIONS β¨
-hβ Show usage info. your classic little "help me" button π-kkey file β Key blob file to read. this is the key file, you're reading it, that's the whole thing π-Oβ Use Well Known Secret for owner password. Default is ask. so like, if you don't pass this, it's gonna ask you. π-pβ Ask for key PIN / password. Default is Well Known Secret. note the flip-flop bestie, this one's the opposite of-Oπ-oβ Ask for SRK PIN / password. Default is Well Known Secret. same deal, but for the SRK πΈ
π¦ EXAMPLES π¦
the classic, just hand over the key file:
stpm-exfiltrate -k ~/.simple-tpm-pk11/my.key
Enter owner password: blah blah
[ ... key data here ...]
now with a key PIN, because you're being a little extra (affectionate):
stpm-exfiltrate -p -k ~/.simple-tpm-pk11/my.key
Enter owner password: blah blah
Enter key PIN: my secret password here
[ ... key data here ...]
and the full serve, owner password and key PIN and SRK PIN, she ate:
stpm-exfiltrate -sp -k ~/.simple-tpm-pk11/my.key
Enter owner password: blah blah
Enter key PIN: my secret password here
Enter SRK PIN: 12345678
[ ... key data here ...]
π DIAGNOSTICS π
Most errors will probably be related to interacting with the TPM chip. like, it's almost always the chip, it's never you (it's sometimes you). Resetting the TPM chip and taking ownership should take care of most of them. See the TPM-TROUBLESHOOTING section of simple-tpm-pk11(7). go read it, it's giving helpful. π§
β SEE ALSO β
simple-tpm-pk11(7), stpm-sign(1), stpm-keygen.
π AUTHOR π
Simple-TPM-PK11 was written By Thomas Habets <habets@google.com> / <thomas@habets.se>.
git clone https://github.com/ThomasHabets/simple-tpm-pk11.git
and that's the whole page, bestie π β this one's from simple-tpm-pk11, dated 16th Febrary, 2014, and yeah I'm keeping that spelling exactly, it's not mine to fix π
π¦ where this page comes from
- debian bookworm: simple-tpm-pk11 0.06-4+b1 Β· Apache-2.0
- debian trixie: simple-tpm-pk11 0.06-5+b1 Β· Apache-2.0
- nixos 26.05: simple-tpm-pk11 0.07
- nixpkgs unstable: simple-tpm-pk11 0.07
- ubuntu jammy: simple-tpm-pk11 0.06-4build1 Β· Apache-2.0
- ubuntu noble: simple-tpm-pk11 0.06-5build2 Β· Apache-2.0
- ubuntu questing: simple-tpm-pk11 0.06-5build2
- ubuntu resolute: simple-tpm-pk11 0.07-1 Β· Apache-2.0
- ubuntu stonking: simple-tpm-pk11 0.07-1build1 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms