-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
stpm-exfiltrate does not return a key or an error #32
Comments
Strange. I'll try to reproduce this. |
Not only am I unable to reproduce this, I can't seem to get
Building
That 0x9 appears to be the only thing the TPM tells the host, which is what we already have in the command output: "operation failed". |
Has there been any changes on this? I'm getting a different error when I try to exfiltrate the key:
This is on a Lenovo T450s, btw.
|
@reanimus maybe you got the owner password wrong? Alt what is your SRK password? |
I double checked and I think I used a hardware key (at least, I assume that's what old me did). Thus, the keys aren't migrateable. |
I've generated a key in software and am now trying to exfiltrate it, but after entering the owner password, the utility returns only
mod=,exp=,key=
Using the key for ssh logins and ssh key signing works fine, I have the dependencies installed, stpm-keygen did not return any errors or warnings during generation, there's no PIN on the ssh key, the SRK password is the well known secret, I've run
tpm_restrictsrk -a
and tried clearing the TPM and starting fresh as well as trying all combinations of the 2 TPM settings I saw in the BIOS ( 'PPI provision override' and 'PPI deprovision override').The OS is Ubuntu 16.04, the issue affects both the version of stpm-exfiltrate from Ubuntu's package repos and the one I got by compiling from git source. The device is a Dell Latitude E5440.
tpm_version
TPM 1.2 Version Info:
Chip Version: 1.2.41.1
Spec Level: 2
Errata Revision: 3
TPM Vendor ID: ATML
TPM Version: 01010000
Manufacturer Info: 41544d4c
The text was updated successfully, but these errors were encountered: