Re: [Trustedjava-support] TPM_NV_INDEX_TRIAL - wrong value

[Michael G. <m.g...@tu...>]

On 05/14/2012 07:31 PM, Michael StJohns wrote:
> Hi --

Hi Michael,

> For some reason, TcTpmConstants.TPM_NV_INDEX_TRIAL has the "D" bit
> set.    This is probably a bug.

I agree that this is not the best value for this constant. It will be 
changed to 0x0000f004 in a future release. Anyhow please note that it's 
a valid index according to the specification.

> I used the constant in TcINvRam.defineSpace (in TcTpmNvData) to see if I
> had space to create a 100 octet space.  What I ended up with was a
> permanent 100 octet space that I can't get rid of.

What exactly do you mean by 'can't get rid of'? According to the TPM 
specification this should not happen. When you try to define an index 
with the D-bit set, a shipped TPM should return TPM_BADINDEX. Which TPM 
do you use? Is the TPM's nvLocked bit set to true? If it is not, then 
D-bit indices can be defined, but also deleted.

Can you please provide the output of the following commands?

jtt tpm_version
jtt tpm_flags
jtt nv_decode --index 0x1000f004

> When I use the correct value - 0xF004 - as the index, I get the
> anticipated behavior.  A "success" results in a return with no creation.

That's what I would have expected ;)

> I'd review all of the TPM_NV_INDEX_* values and make sure you're using
> the correct values.

Both versions with and without D-bit set are correct. For compatibility 
reasons the other constants will remain unchanged.

> Mike

HTH,
Michael