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

[SPIN]

you won't need to...

"sanity" comes from the Dew Drop Inn. how ironic that the Inn's proprietor accuses me of "juggling games" (as a pejorative) when his consuming passion is a company which uses a juggler as its corporate identity!

the bottom line is that i own a lot of shares & was/am worried by today's MSFT PR. if it makes the Wave Nation more comfortable to think my posts are a ruse, by all means think that.

thanks for all the insightful analysis to demonstrate why this is not a considerable threat, a threat that did not exist in this little universe a day ago.

i'll just lurk & trade it... but i meant no harm today whatsoever & think the reaction speaks volumes about things here...

later.

edit: the "Wavoid Bar & Grille" is about as lame as it gets! thank Gawd there is no cover charge!

[Wildman262]

Rosie, make no mistake. MSFT needs hardware for NGSCB. As it stands now, that means a TPM on the MB, a chip in the keyboard and monitor. (I think there was also at least one other secure chip requirement for NGSCB)

It's very likely that Siden is still there, alive and well. For NGSCB, authentication, logon etc. will take place in a Longhorn in a trusted environment. The keyboard chip simply encrypts the keystrokes, and then sends it via USB to NGSCB where the actual decryption and authentication take place. The keyboard on it's own does nothing without NGSCB. It can not support any services or do any authentication.

Finread requires that the authentication takes place in the reader/keyboard, nor could Finread be supported with the above kind of keyboard. Wave has the TPM's covered via their relationships with Intels,NSM, INFX, ATML, because Wave's applicatons and utility products will use the TPM's from the above vendors and be compatible with NGSCB computers when they hit the market.

MSFT will need still need the keyboard chips for NGSCB, but they won't need them until they start doing betas.