Sorry for my unconventional response to my previous post. I tried the web way 
but it kept complaining 
of an 80 character limit exceeded no matter how I edited.

My solution was simply to upgrade from 0.3.9 to 0.3.10 of Trousers. I suspect 
the person in January and
February of this year did not "solve" his problem merely by rebuilding Trousers 
with debug. I suspect his
solution was by upgrading to 0.3.10 like mine. He had the exact same issues as 
me. 

I discovered this by finding out on my successful installation on a different 
form of hardware, I had 0.3.10
Trousers. However I looked through the tar files I used on my yocto and noticed 
0.3.9 was the version for 
Trousers for the build I put on the Kontron.

I looked at some of the archives for the release notes on 0.3.10 - by Kent 
Yoder. The fixes were very 
similar to what was needed to solve my problem. 

I'm not only a newbie on Trousers, but a newbie on Yocto and Linux as well.

Thanks for a great resource - this users group!

Bill Martin


From: Bill Martin <bmartin <at> valicore.com>
Subject: tpm_takeownership and private key from previous OS
Newsgroups: gmane.comp.encryption.trousers.user
Date: 2013-08-07 15:07:26 GMT (5 days and 3 minutes ago)
Hi folks,

I have a yocto-built system running on a Kontron (arch is i686). I explicitly 
instructed the yocto to bring
in tpm-tools and TrouSerS. And I know they are installed. I set my BIOS to 
clear the tpm, brought up the
system again, and noticed /sys/class/misc/tpm0/device/pubek is empty. That was 
to be expected. Next I
enabled the TPM in bios and reset the Kontron. After the power came up I 
noticed pubek was not empty.
Moreover, I could do the tpm_version but my tpm_takeownership failed.

I did a lot of looking through search engines and saw earlier this year in 
February someone suggested to
rebuild TrouSerS with debug and see what is happening. That rebuild seemed to 
work for him.

But in my case I am wondering if a previous private key was installed in 
Kontron's TPM chip, which would make
the tpm_takeonership useless? Here's what I got...

root <at> crownbay-noemgd:~# tpm_takeownership -l debug
Tspi_Context_Create success
Enter owner password: 
Confirm password: 
Enter SRK password: 
Confirm password: 
Tspi_Context_Connect success
Tspi_Context_GetTpmObject success
Tspi_GetPolicyObject success
Tspi_Policy_SetSecret success
Tspi_Context_CreateObject success
Tspi_GetPolicyObject success
Tspi_Policy_SetSecret success
Tspi_TPM_TakeOwnership failed: 0x00002004 - layer=tcs, code=0004 (4), Internal 
software error
Tspi_Context_CloseObject success
Tspi_Context_FreeMemory success
Tspi_Context_Close success

thanks in advance

Bill Martin
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
TrouSerS-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/trousers-users

Reply via email to