Replies to post #57784 on Wave Systems Corp. (fka WAVXQ)

[awk]

btk: Really think someone is going to read your stuff?

Get real, man!

[SheldonLevine]

CryptoAPI and CSP's

dig space, your diagram is correct.

Wave's CSP "plugs in" to the architecture BELOW the CryptoAPI layer. This allows Win32 apps developers to develop against the standardized CryptoAPI and subsequently enable Wave's CSP in order to provide a different IMPLEMENTATION for the functionality requested (in Wave's case, using the TPM).

As I have stated in the recent past, there is a big difference between a standardized interface and the implementation of the functionality for that interface. I am re-iterating this point since this seems to be confusing to some posters here.

The last paragraph of this article is important.
http://msdn.microsoft.com/library/en-us/seccrypto/security/cryptoapi_system_architecture.asp?frame=t...

Some more general information about CSP's and the cryptography process
http://msdn.microsoft.com/library/en-us/seccrypto/security/csps_and_the_cryptography_process.asp?fra...

Not trying to stir the pot, only to help clarify for those who are interested.

Regards

SL

[Doma]

dig space...................NTRU

"I have said that NTRUs CTSS' ability to operate on all TPM was an important component of interoperability."

Atmel TPMs work with IBM's TSS & NTRU's TSS.
NSM TPMs work with IBM's TSS & NTRU's TSS.
Infineon's TSS works with Broadcom & Infineon TPMs.

Exactly What makes NTRU's TSS Interoperable with
ALL TPM's & IBM & Infineon's TSS NOT???????????

All TPM's Can work with All TSS's....

My "maybe" dig was in relation to Who had to
do the work......the TPM manufacturer or the
TSS manufacturer........it's mo it's the TPM
manufacturer!

Doma.