From: FIXED-TERM Schick Felix (CR/APA3) <fixed-term.Felix.Schick3 at bosch.com>
To: tpm2@lists.01.org
Subject: [tpm2] Esys primary key creation error
Date: Thu, 20 Aug 2020 13:53:41 +0000 [thread overview]
Message-ID: <f82e7dfe9a2e4f5a8e3b1eb4a9a93bbc@bosch.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
Hello Everybody,
I am currently experimenting with the Esys-API and have encountered a problem during the primary key creation.
TPM2B_PUBLIC * primaryOutPublic;
TPM2B_CREATION_DATA * primaryCreationData;
TPM2B_DIGEST * primaryCreationHash;
TPMT_TK_CREATION * primaryCreationTicket;
ESYS_TR primaryObjectHandle;
// Create primary key
rc = Esys_CreatePrimary(esysContext, ESYS_TR_RH_OWNER, ESYS_TR_NONE, ESYS_TR_NONE, ESYS_TR_NONE,
&primaryInSensitive, &primaryInPublic, &outsideInfo, &creationPCR,
&primaryObjectHandle, &primaryOutPublic, &primaryCreationData, &primaryCreationHash, &primaryCreationTicket);
if( rc != TSS2_RC_SUCCESS){
std::cerr << "Creation of primary key failed with " <<
"response code: 0x"<< std::hex << rc << std::endl;
Esys_Finalize(&esysContext);
return EXIT_FAILURE;
}
I get the following error:
ERROR:esys:src/tss2-esys/esys_iutil.c:1178:check_session_feasibility() Not enough sessions provided for the command.
ERROR:esys:src/tss2-esys/api/Esys_CreatePrimary.c:208:Esys_CreatePrimary_Async() Check session usage ErrorCode (0x0007000b)
ERROR:esys:src/tss2-esys/api/Esys_CreatePrimary.c:110:Esys_CreatePrimary() Error in async function ErrorCode (0x0007000b)
I hope this is enough context for the trained eye, I would be very grateful for help with this issue.
Thank you very much
Felix Schick
[-- Attachment #2: attachment.htm --]
[-- Type: text/html, Size: 7812 bytes --]
reply other threads:[~2020-08-20 13:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f82e7dfe9a2e4f5a8e3b1eb4a9a93bbc@bosch.com \
--to=tpm2@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox