-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Device enrollment fails on Linux: integrity check failed #53357
Comments
What OS/version is running on the affected workstation? |
Hi @zmb3 I have downloaded the same package that we use in Ubuntu teleport-ent-v17.2.8-linux-amd64-fips-bin.tar.gz |
I tried to recreate this error in a ProxMox VM with a vTPM. I was able to successfully enroll the device. Here is what I did. I imported the ArchLinux cloudinit qcow2 image to a ProxMox template using this script, and set basic options like disk size, core count, network, etc.: Shell script to import an Arch Template to proxmox
Next, I cloned the template a new VM, and then manually added the TPM device using the web interface. It prompted me to also add a TPM state disk. I installed I also had to add the default The raw config as seen by `qm config VMID` output:
The output of `sudo dmidecode`
Output of `sudo pacman -Q` (package listing with versions)
After running
@apast0r Any other info you could share about the TPM, or other software making use of it would be great. |
Hi @programmerq I paste more information: User membership of tss
Teleport binaries:
Current system boot config:
PCRS contents:
I have cleared the TPM persistent objects and try to enroll:
|
Expected behavior:
Running the command:
tsh device enroll --current-device -d
, should enroll the device.Current behavior:
The command exit with error "
cannot load attestation key: Load() failed: parameter 1, error code 0x1f : integrity check failed
"Bug details:
Error trace:
I found a similar issue in the repo page of the library that teleport uses: "error code 0x1f : integrity check failed" while loading an AK created with the ECC ParentKeyConfig
The text was updated successfully, but these errors were encountered: