I correct myself. It seems that sealing and attestation requests can only be done only through accessting the TSS implementation. Other TPM functionality, such as encryption, decryption and digital signatures can be accessed through the PKCS#11 interface.
The TPM is the trusted base for the computer - in theory it is supposed to be a piece of hardware that is protected from physical tampering (not quite so in practice), that can securely store secrets, and that is trusted to do some basic cryptographic functions without being compromised. One of th
I tested your patch and it works.
thanks
rob
From: Nelson B <[EMAIL PROTECTED]>
To: dev-tech-crypto@lists.mozilla.org
Subject: Re: pkcs11 default provider
Date: Wed, 22 Feb 2006 10:14:20 -0800
robert dugal wrote:
> I will enter the modutil bug report today. I tried modifying modutil to
> se
Peter Djalaliev wrote:
> The original TSS (Trusted Software Stack) implementation (libtcpa by
> IBM) doesn't use PKCS#11 calls and this is the library that we are
> using. Even though a PKCS#11-based implementation exists now
> (TrouSers), I don't quite have the ability (time) to switch right now
4 matches
Mail list logo
