https://github.com/tpm2-software/tpm2-tss/issues/2889
https://github.com/tpm2-software/tpm2-tools/pull/3426/commits
Indeed, hardcoding size = 14 as mentioned in the github issue does push
this command through to completion and works for me on subsequent boots
when using TPM to unlock encrypted vo
# Steps to reproduce
## On fresh/Updated Jammy instance (no fips)
ubuntu@jammy-05-dsk-crypt:~$ sudo apt install -y tpm2-tools
ubuntu@jammy-05-dsk-crypt:~$ sudo tpm2_nvdefine -s 64 0x1500016
nv-index: 0x1500016
ubuntu@jammy-05-dsk-crypt:~$ cat /dev/urandom | tr -dc 'a-zA-Z0-9' | head -c 64
> key.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: tpm2-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2074270
Title:
** Description changed:
Release: 22.04 with fips-updates
-
- Symptom: Use of TPM2 tools fails with error code 0x70001 (e.g., `tpm2_clear`,
`tpm2_nvdefine 0x1500018 -C o -s 32`). I assume this is an incompatibility
between tpm2-tools (5.2-1build1) and the fips OpenSSL package
(3.0.5-0ubun
