I managed to get to the bottom of that problem.
It was indeed that there were too many resources in use.
Once I freed some up  Tspi_NV_DefineSpace completed successfully.

I now have the following situation:

It has an encrypted root file system and an encrypted swap partition.
The machine boots with TrustedGrub and TrustedGrub detects the TPM module.
tpm-luks is installed and tpm-luks-init completed successfully.
tpm-luks-init successfully saved encryption keys for each of the two  
encrypted partitions to the TPM module.
It all looks good.
However, linux still prompts for the encryption password at boot-time.

Any suggestions on where I should be looking for the source of the problem?

The following is run on boot:
cryptsetup luksOpen /dev/sda2 rootcrypt

Is there something different I should be doing to read the key from the  
TPM?
The cryptsetup FAQ suggests that I should get cryptsetup read the key from  
STDIN that is written by something that reads the value from the TPM.
However, I haven't found any examples of this anywhere.

Thanks,
Conor


On Tue, 25 Feb 2014 19:39:52 -0000, Richard <[email protected]>  
wrote:
> Connor,
>I'm trying to reproduce this using a software TPM, since mine doesn't 
> have NVRAM space. But from the look of it, the tpm-luks-init is tryingto  
> use too many resources or another programming is sharing theresources  
> with it. Do you have any other application which uses TPM -specifically,  
> the tpm nvram?

------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
TrouSerS-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/trousers-users

Reply via email to