Thanks Bill.

Wondering why this would fail. The external make credential API,  I have taken from tss2 GitHub only why would secret fail? When I ran all of this locally it worked, the moment I moved the make external credential to the server Im hitting this?

Can it be because of OpenSSL 1.1.0 required in tss2 and 1.0.2 version running on my server?

Thanks

Rahul

On Tue, Mar 10, 2020 at 3:36 PM Roberts, William C <william.c.roberts@intel.com> wrote:

The error codes encode a bunch of values, so you won't see that value via a straight grep.

But you can use tpm2_rc_decode from the tpm2-tools project, like so:
$ tpm2_rc_decode 0x2c4
tpm:parameter(2):value is out of range or is not correct for the contex

See the tools project:
https://github.com/tpm2-software/tpm2-tools

Note that the commands specification will show you what parameter 2 is:
https://trustedcomputinggroup.org/wp-content/uploads/TPM-Rev-2.0-Part-3-Commands-01.38.pdf

Everything after the triple line starts the parameters starting at index 1.
So in this case the secret parameter is wrong.

Note that since TSS version 2.3.0 a software library was also added
for converting these return codes to more human understandable strings,
The header file is here:
https://github.com/tpm2-software/tpm2-tss/blob/master/include/tss2/tss2_rc.h

and then you just link against lib tss2-rc, just in case you needed this built into
your program.

Bill

> -----Original Message-----
> From: Rahul Hardikar [mailto:rahulhardikar@gmail.com]
> Sent: Tuesday, March 10, 2020 5:02 PM
> To: tpm2@lists.01.org
> Subject: [tpm2] ESys_ActivateCredential
>
>
> Hi All,
> What does it mean when Esys_ActivateCredential returns 0x2c4? I don't see this
> error defined anywhere.
>
> Thanks,
> Rahul