"Xu Yongjiang" <[EMAIL PROTECTED]> wrote: > > PKCS#11 is a set of specification of interface. Maybe there is no > defined module, except for PKCS#11 self. >
To clarify again (and apologies to those who have seen this before), PKCS#11 is an API called by the application software in your system. PKCS#11 makes no assumptions about the way in which cryptographic services are provided - they can be in a smart card, or entirely within software in the same system, or at the other end of a network link. It is PKCS#15 that has started to define a common way in which a smart card can be used to provide the crypto services. And, as far as I know, it is the MUSCLE community and David C that is furthest ahead with linking PKCS#11, PKCS#15 and the structure of implementations in cards into an open (and therefore potentially fully interoperable) architecture. Working in the European community of specification developers, I'm very grateful for this open way of thinking. Merry Xmas Peter T Bristol UK PS Has anyone got any further with unearthing the DoD spec discussed in other posts? *************************************************************** Unix Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/ To unsubscribe send an email to [EMAIL PROTECTED] with unsubscribe sclinux ***************************************************************
