Jürgen Repp

@dadiestfish2077 tpm2_tools 5.2 and tss 3.0.2 are the versions available on ubuntu 22.04. I tested you example with these two versions but could not reproduce the error.

@dadiestfish2077 I have tried it with qemu and swtpm used to create a TPM device. It worked there too. Does the error also occur after: ``` tpm2_changeauth -c o newpass...

You did not specify the data to seal (-i) when you executed `tpm2_create` for `key.obj.priv` So no keyed hash object is created and the error `0x18a` will be produced. P.S....

Your example worked if -i was used. So If -i is not used a normal key will be created. Actions with this key will be protected by the policy you...

Trusted keys are symmetric keys generated by the kernel which are sealed by a TPM key as parent. In your example 0x81000001. I think the pcr policy for the sealed...

@gotthardp Any idea?

@akorb The command seems to be work in progress. As a first step I have added padding guessing.

TPM2_ALG_SHA and TPM2_ALG_SHA1 both have the value 0x4. So that can't be the reason. Unfortunately the bad value is not displayed. Would it be possible for you to replace the...

@MartinLoeper It also would be interesting what TPM you are using.

@MartinLoeper Could you please also attach the output of `tpm2_getcap algorithms`. If that command works with your TPM we should see the alg id which causes the problem.