Wave Systems Corp. (fka WAVXQ)

[dig space]

goin,

MSFT addressing each individual vendor is being a shim, by definition, no?

Now, is this a thingy they could put in a box and sell to MSCAPI developers, beats me.

I was replying to awk slide of TPM 2.0, msft providing the "Microsoft TPM stack",

The current infrastructure on the left shows "direct TPM commands" which in practice require shimming of MSCAPI to TSS, and on the right it looks like the rich OS has finally decided to take care of that in TPM v 2.0, moreover the slide seems to imply the rich OS handling v1.2 and v2.0 interoperability.

I could see some legacy Wave shims in all of that, but that's about it.