tpm2-tss question
by Yasuhiro Hosoda
MY name is Yasuhiro Hosoda.
I am developing a program using TSS1.0(Nov１．2016).
I encountered a problem with PolicySecret error 0x98e and need help.
My program uses tpmtest.cpp as a base of development.
The situation is as follows:
1 Create TPM Keys like this.
EK
｜--------
｜ |
MK AK
｜
SK
2 Execute PolicySecret twice using HMAC session. At first, it ends
without error. Then it ends with 0x98e
For clarification, I print out the values of Virtual Handle and Real Handle.
The value of Virtual/Real Handles differ at 2nd excution of the command.
(See NO 25/26 Below)
I understand that the resource manager assigns Virtual Handle and my
program calculates HMAC using that handles.
On the other hand, TPM may calculate HMAC using Real Handle.
That is my hypothesis.
Any suggestion about the usage of Session Handle?
NO Command Virtual/Real Handle LOC
1. CreatePrimary(EK) real=80000000, virtual=80000000 8381
2. HierarchyChangeAuth1 8421
3. HierarchyChangeAuth2 8431
4. StartAuthSession(Policy) real=3000000, virtual=3000000 8480
5. PolicySecret(ENDORSEMENT) 8494
6. Create(MK) 8515
7. PolicySecret(ENDORSEMENT) 8529
8. Load(MK) real=80000001, virtual=80000001 8542
9. Evict(MK) 8552
10. Create(SK) 8590
11. Load(SK) real=80000001, virtual=80000002 8598
12. PolicySecret(ENDORSEMENT) 8609
13. Create(AK) 8635
14. PolicySecret(ENDORSEMENT) 8645
15. Load(AK) real=80000001, virtual=80000003 8655
16. FlushContext(POLICY) 8664
17. StartAuthSession(POLICY) real=3000000, virtual=3000000 8668
18. StartAuthSession(HMAC) real=2000001, virtual=2000001 8678
19. ComputeCommandHMAC(LoadExternal) real=80000000, virtual=80000004 3706
20. ComputeCommandHMAC(HMAC_Start) real=80000001, virtual=80000005 3706
21. PolicySecret(SK) 8711
22. FlushContext(HMAC) 8717
23. FlushContext(POLICY) 8724
24. CertifyCreation(SK) 8738
25. StartAuthSession(POLICY) real=3000000, virtual=3000001 8745
26. StartAuthSession(HMAC) real=2000001, virtual=2000000 8754
27. ComputeCommandHMAC(LoadExternal) real=80000000, virtual=80000005 8782
28. ComputeCommandHMAC(HMAC_Start) real=80000001, virtual=80000004 8782
29. PolicySecret(SK) 8789
The whole source program can be found here.
https://github.com/intel/tpm2-tss/files/1516612/tpmtest.cpp_0x98e_2.txt
Kind regards,
--
Yasuhiro Hosoda
NTT Electronics Corporation （NEL)
Security Support Project
2 years, 2 months
TPM2TSS engine for OpenSSL
by Fuchs, Andreas
Hi all,
I just wanted to announce that we pushed a new crypto engine for OpenSSL using the tpm2-tss software stack.
It is licensed under the BSD 3-clause license.
It currently includes RSA sign, RSA decrypt and ECDSA with TPM generated keys.
It uses ESAPI/ESYS (so it's a good usage example) and thus relies on the 2.0 series of tpm2-tss.
I'd like to see some testing and bug reports if you don't mind.
You can find the project here: https://github.com/tpm2-software/tpm2-tss-engine
Big thanks to Infineon for sponsoring this work !
Best regards,
Andreas Fuchs
2 years, 4 months
tools: tcti init allocation route failed for library "tabrmd"
by Scheie, Peter M
I'm trying to get the tools working with the emulator, on a CentOS 7 VM. I've got tss 2.0.0, abrmd 2.0.0, tools 3.1.0, and the IBM emulator 1119. Everything compiles and installs okay, the emulator is running, I start abrmd with 'sudo -u tss /tmp/tpm2/sbin/tpm2-abrmd --tcti=libtss2-tcti-mssim.s' and the emulator says 'Client accepted'. However, when I then run, say, tpm2_pcrlist, I get this error:
WARNING: Failed to create connection with service: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
ERROR: tcti init allocation routine failed for library: "tabrmd" options: "(null)"
ERROR: Could not load tcti, got: "tabrmd"
And then abrmd crashes, while the emulator reports 'read() error. Error is 2 No such file or directory'.
Suggestions?
2 years, 6 months
Choosing PCR banks for swtpm's TPM 2
by Stefan Berger
Hi!
I am sending this email to solicit input on the choice of the PCR
banks to enable for swtpm's TPM 2. I have currently enabled 4 PCR banks
for SHA{1,256,384,512}. The downside of this is that running the TPM 2
with so many PCR banks has a performance impact when the Linux integrity
measurement architecture is used and has to extend measurements into all
PCR banks, which Linux does already.
TPM 2 has the PCR_Allocate() command for a user to select the PCR banks
to use. This command allows to make some PCR banks invisible. The change
has to be done through the firmware and has the downside that the TPM2
does not support TPM2_Shutdown(SU_STATE) after this command was used.
This prevents suspend/resume from working properly. So, it seems that
one shouldn't have to use this command, which in turn means the number
of PCR banks should be small.
Another complication with the swtpm is the upgrade path. Suspended VMs
will expect that the PCR banks that were available before the suspend
will be available after the resume and a possible swtpm upgrade. This in
turn means that the PCR banks should be chosen now and we'll have to
stick with them.
That said, my suggestion would be to enable only PCR banks for SHA256
for 'now' and SHA512 for the future. Having two PCR banks should enable
decent performance. If someone wants to have better performance he will
have to go through the firmware to select the PCR banks at the expense
of loosing suspend/resume support.
The change of PCR banks for the current 4 PCR banks will break the state
of all swtpms.
If you have suggestions, please let me know.
Regards,
Stefan
2 years, 6 months
What is the exact meaning of "parameters" in cpHash?
by Tianyu Qi
Hi,
I am writing implementation of TPM2_Load. When writing cpHash in computing HMAC, I saw cpHash description in TPM-Rev-2.0-Part-1-Architecture-01.38 mentioned there is a "parameters" parameter at last, which represents remaining command parameters. Since the cpHash will use commandCode as the first parameter, does this "parameters" means every parameter in the command? For example, in TPM2_Load, I need to add tag, commandSize, parentHandle, inPublic and inPrivate? If so, should I add the authorization structure after parentHandle?
Regards and thanks,
Tianyu Qi
(+1) 315 278-2725
EECS Department, Syracuse University
2 years, 6 months
Re: [tpm2] [Qemu-devel] Choosing PCR banks for swtpm's TPM 2
by Stefan Berger
On 06/25/2018 12:11 PM, Dr. David Alan Gilbert wrote:
> * Stefan Berger (stefanb(a)linux.vnet.ibm.com) wrote:
>> On 06/25/2018 11:29 AM, Dr. David Alan Gilbert wrote:
>>> * Stefan Berger (stefanb(a)linux.vnet.ibm.com) wrote:
>>>> On 06/25/2018 11:18 AM, Dr. David Alan Gilbert wrote:
>>>>> * Stefan Berger (stefanb(a)linux.vnet.ibm.com) wrote:
>>>>>> Hi!
>>>>>>
>>>>>> I am sending this email to solicit input on the choice of the PCR banks to
>>>>>> enable for swtpm's TPM 2. I have currently enabled 4 PCR banks for
>>>>>> SHA{1,256,384,512}. The downside of this is that running the TPM 2 with so
>>>>>> many PCR banks has a performance impact when the Linux integrity measurement
>>>>>> architecture is used and has to extend measurements into all PCR banks,
>>>>>> which Linux does already.
>>>>>>
>>>>>> TPM 2 has the PCR_Allocate() command for a user to select the PCR banks to
>>>>>> use. This command allows to make some PCR banks invisible. The change has to
>>>>>> be done through the firmware and has the downside that the TPM2 does not
>>>>>> support TPM2_Shutdown(SU_STATE) after this command was used. This prevents
>>>>>> suspend/resume from working properly. So, it seems that one shouldn't have
>>>>>> to use this command, which in turn means the number of PCR banks should be
>>>>>> small.
>>>>>>
>>>>>> Another complication with the swtpm is the upgrade path. Suspended VMs will
>>>>>> expect that the PCR banks that were available before the suspend will be
>>>>>> available after the resume and a possible swtpm upgrade. This in turn means
>>>>>> that the PCR banks should be chosen now and we'll have to stick with them.
>>>>>>
>>>>>> That said, my suggestion would be to enable only PCR banks for SHA256 for
>>>>>> 'now' and SHA512 for the future. Having two PCR banks should enable decent
>>>>>> performance. If someone wants to have better performance he will have to go
>>>>>> through the firmware to select the PCR banks at the expense of loosing
>>>>>> suspend/resume support.
>>>>>>
>>>>>> The change of PCR banks for the current 4 PCR banks will break the state of
>>>>>> all swtpms.
>>>>>>
>>>>>> If you have suggestions, please let me know.
>>>>> Is this something that has to be set at compile time or could it be
>>>>> something chosen at run time (as options to the swtpm command line?)
>>>> It is a compile-time option...
>>> Hmm, that's a shame - I was hoping you'd be able to switch them at
>>> runtime (or at least hide them?) then you can solve the upgrade problem
>>> by running the new swtpm with a flag telling it to hide the new banks.
>>> I hope the ondisk formats for suspend/resume/migration are descriptive
>>> enough to be able to spot an error if you try and load one configured
>>> differently.4
>> The disk format does detect it and refuses to take the state if either there
>> are too many PCR banks or not enough.
> What happens if there are the right number just the wrong type?
The state would be rejected since they are incompatible.
>
>> For the initial version of swtpm we would need to define a default set of
>> PCR banks since the TPM 2 code uses compile time options to build in that
>> set of PCR banks.
> You talk of PCR_Allocate() above as a spec-defined command to hide PCRs
> but with the downside of breaking TPM2_Shutdown - could you implement
> something from the commandline without that downside (I don't know how
> PCR banks work).
Like I said, during swtpm_setup TPM 2 manufacturing the set of PCR banks
would be chosen and that set would be used by that TPM 2 from then on.
Though this flexibility is not supported by the code today.
>
>> A future version of swtpm could expose command line options for selecting
>> the PCR banks an instance of swtpm is to run with. libtpms would be compiled
>> with support for all of them and only the chosen subset would be active
>> starting with the initial creation of a particular instance of swtpm.
> Right, that would solve the upgrade half of the problem.
For now I think an initial set of banks to go with would be appropriate.
Stefan
2 years, 6 months
Re: [tpm2] [Qemu-devel] Choosing PCR banks for swtpm's TPM 2
by Stefan Berger
On 06/25/2018 12:10 PM, Daniel P. Berrangé wrote:
> On Mon, Jun 25, 2018 at 12:08:34PM -0400, Stefan Berger wrote:
>> On 06/25/2018 11:59 AM, Daniel P. Berrangé wrote:
>>> On Mon, Jun 25, 2018 at 11:56:24AM -0400, Stefan Berger wrote:
>>>> On 06/25/2018 11:25 AM, Daniel P. Berrangé wrote:
>>>>> On Mon, Jun 25, 2018 at 11:05:55AM -0400, Stefan Berger wrote:
>>>>>> Hi!
>>>>>>
>>>>>> I am sending this email to solicit input on the choice of the PCR banks to
>>>>>> enable for swtpm's TPM 2. I have currently enabled 4 PCR banks for
>>>>>> SHA{1,256,384,512}. The downside of this is that running the TPM 2 with so
>>>>>> many PCR banks has a performance impact when the Linux integrity measurement
>>>>>> architecture is used and has to extend measurements into all PCR banks,
>>>>>> which Linux does already.
>>>>>>
>>>>>> TPM 2 has the PCR_Allocate() command for a user to select the PCR banks to
>>>>>> use. This command allows to make some PCR banks invisible. The change has to
>>>>>> be done through the firmware and has the downside that the TPM2 does not
>>>>>> support TPM2_Shutdown(SU_STATE) after this command was used. This prevents
>>>>>> suspend/resume from working properly. So, it seems that one shouldn't have
>>>>>> to use this command, which in turn means the number of PCR banks should be
>>>>>> small.
>>>>>>
>>>>>> Another complication with the swtpm is the upgrade path. Suspended VMs will
>>>>>> expect that the PCR banks that were available before the suspend will be
>>>>>> available after the resume and a possible swtpm upgrade. This in turn means
>>>>>> that the PCR banks should be chosen now and we'll have to stick with them.
>>>>> Anything that has a risk of needing to change between versions would need
>>>>> to be tied into the machine type in some way.
>>>> You mean a machine type like q35? I am not sure how it would be tied into
>>>> QEMU since the swtpm command line options are chosen more or less
>>>> independently of the ones from QEMU.
>>> Yes, each QEMU release introduces a new versioned machine type eg
>>> q35-2.10, q35-2.11, q35-2.12, q35-3.0
>>>
>>> If anything in QEMU changes which impacts live migraiton/save/restore/etc
>>> then we tie it to the versioned machine type. so q35-3.0 would get the
>>> new default value, and all previous machine types keep the old default
>>> value.
>>>
>>> For this to be possible with externally launched swtpm though, would
>>> require some way for QEMU to talk to swtpm to tell it what default
>>> to use for this. I don't know enough about swtpm to have an idea how
>>> practical this is or not.
>> The set of PCR banks a future TPM 2 would be 'manufactured with' would be
>> determined by parameters to swtpm_setup. That's when the TPM2 is
>> 'manufactured' and the certificates are created and written into its NVRAM
>> locations. QEMU is not talking to the TPM 2 at this point. So it would be
>> parameters passed from libvirt to swtpm_setup that determine the set of PCR
>> banks. swtpm itself would get those supplied via command line options when
>> invoked by swtpm_setup. If one was to skip over the swtpm_setup step, then
>> why not use the swtpm command line options that need to be there for
>> swtpm_setup support. Though I think few people will use it like that. I
>> would not extend the protocol for this purpose.
> Ah so in that case, we would merely require ability to record the desired
> PCR setup in the XML, and libvirt would then pass the right args to
> swtpm_setup when required.
Yes, the user would choose PCR banks or libvirt probes swtpm_setup
version/command line options and selects a reasonable set for the hash
algorithms recommended at that time.
Stefan
>
> Regards,
> Daniel
2 years, 6 months
Re: [tpm2] [Qemu-devel] Choosing PCR banks for swtpm's TPM 2
by Stefan Berger
On 06/25/2018 11:59 AM, Daniel P. Berrangé wrote:
> On Mon, Jun 25, 2018 at 11:56:24AM -0400, Stefan Berger wrote:
>> On 06/25/2018 11:25 AM, Daniel P. Berrangé wrote:
>>> On Mon, Jun 25, 2018 at 11:05:55AM -0400, Stefan Berger wrote:
>>>> Hi!
>>>>
>>>> I am sending this email to solicit input on the choice of the PCR banks to
>>>> enable for swtpm's TPM 2. I have currently enabled 4 PCR banks for
>>>> SHA{1,256,384,512}. The downside of this is that running the TPM 2 with so
>>>> many PCR banks has a performance impact when the Linux integrity measurement
>>>> architecture is used and has to extend measurements into all PCR banks,
>>>> which Linux does already.
>>>>
>>>> TPM 2 has the PCR_Allocate() command for a user to select the PCR banks to
>>>> use. This command allows to make some PCR banks invisible. The change has to
>>>> be done through the firmware and has the downside that the TPM2 does not
>>>> support TPM2_Shutdown(SU_STATE) after this command was used. This prevents
>>>> suspend/resume from working properly. So, it seems that one shouldn't have
>>>> to use this command, which in turn means the number of PCR banks should be
>>>> small.
>>>>
>>>> Another complication with the swtpm is the upgrade path. Suspended VMs will
>>>> expect that the PCR banks that were available before the suspend will be
>>>> available after the resume and a possible swtpm upgrade. This in turn means
>>>> that the PCR banks should be chosen now and we'll have to stick with them.
>>> Anything that has a risk of needing to change between versions would need
>>> to be tied into the machine type in some way.
>> You mean a machine type like q35? I am not sure how it would be tied into
>> QEMU since the swtpm command line options are chosen more or less
>> independently of the ones from QEMU.
> Yes, each QEMU release introduces a new versioned machine type eg
> q35-2.10, q35-2.11, q35-2.12, q35-3.0
>
> If anything in QEMU changes which impacts live migraiton/save/restore/etc
> then we tie it to the versioned machine type. so q35-3.0 would get the
> new default value, and all previous machine types keep the old default
> value.
>
> For this to be possible with externally launched swtpm though, would
> require some way for QEMU to talk to swtpm to tell it what default
> to use for this. I don't know enough about swtpm to have an idea how
> practical this is or not.
The set of PCR banks a future TPM 2 would be 'manufactured with' would
be determined by parameters to swtpm_setup. That's when the TPM2 is
'manufactured' and the certificates are created and written into its
NVRAM locations. QEMU is not talking to the TPM 2 at this point. So it
would be parameters passed from libvirt to swtpm_setup that determine
the set of PCR banks. swtpm itself would get those supplied via command
line options when invoked by swtpm_setup. If one was to skip over the
swtpm_setup step, then why not use the swtpm command line options that
need to be there for swtpm_setup support. Though I think few people will
use it like that. I would not extend the protocol for this purpose.
Stefan
>
> Regards,
> Daniel
2 years, 6 months
Re: [tpm2] [Qemu-devel] Choosing PCR banks for swtpm's TPM 2
by Stefan Berger
On 06/25/2018 11:25 AM, Daniel P. Berrangé wrote:
> On Mon, Jun 25, 2018 at 11:05:55AM -0400, Stefan Berger wrote:
>> Hi!
>>
>> I am sending this email to solicit input on the choice of the PCR banks to
>> enable for swtpm's TPM 2. I have currently enabled 4 PCR banks for
>> SHA{1,256,384,512}. The downside of this is that running the TPM 2 with so
>> many PCR banks has a performance impact when the Linux integrity measurement
>> architecture is used and has to extend measurements into all PCR banks,
>> which Linux does already.
>>
>> TPM 2 has the PCR_Allocate() command for a user to select the PCR banks to
>> use. This command allows to make some PCR banks invisible. The change has to
>> be done through the firmware and has the downside that the TPM2 does not
>> support TPM2_Shutdown(SU_STATE) after this command was used. This prevents
>> suspend/resume from working properly. So, it seems that one shouldn't have
>> to use this command, which in turn means the number of PCR banks should be
>> small.
>>
>> Another complication with the swtpm is the upgrade path. Suspended VMs will
>> expect that the PCR banks that were available before the suspend will be
>> available after the resume and a possible swtpm upgrade. This in turn means
>> that the PCR banks should be chosen now and we'll have to stick with them.
> Anything that has a risk of needing to change between versions would need
> to be tied into the machine type in some way.
You mean a machine type like q35? I am not sure how it would be tied
into QEMU since the swtpm command line options are chosen more or less
independently of the ones from QEMU.
Stefan
2 years, 6 months
