Hi Anders, Anders Rundgren wrote: > If you wanted to provide a USB PKI token that would give the user maximum > flexibility it seems that the device should support CCID. > > 1. As I understand,CCID only provides the basic communication and does not > address higher level issues such as PKI, right? > > 2. Would a token that emulates FIPS201 and CCID be usable in most > systems as is or is there another emulation that would be better? > > 3. You would need to "hijack" somebody else ATR in order to emulate > in a (for the user) hassle-free way? > > 4. Other question: CCID allows you to exchange arbitrary data between > the token and the host, right? > >
most of this information can easily be found using YourFavouriteSearchEngine, e.g. http://www.smartcardalliance.org/newsletter/february_2005/feature_0205.html CCID: The Chip Card Interface Device (CCID) specification is an approach to smart card reader communication that is gaining in popularity. The specification defines a standard communication protocol for smart card readers that connect to a computer via USB, allowing the same host-side driver to communicate with any CCID-compliant smart card reader. Microsoft provides a CCID driver through the Windows Update system. All new smart card reader deployments should seriously consider using CCID-compliant readers, both to reduce driver installation issues and to ensure that, in the future, the installed smart card readers can be easily and transparently replaced with any other CCID-compliant reader. PC/SC: The basic technology for communication between personal computers and smart cards is PC/SC, defined by the PC/SC Workgroup (www.pcscworkgroup.com). PC/SC defines an application program interface (API) that provides software developers with a standard set of tools for managing smart card readers and communicating with readers and cards. The PC/SC interface defines standard interfaces for a variety of smart card related-operations. The most common are: * Enumerating and describing attached smart card readers * Requesting information about card and reader states * Exchanging commands with cards Microsoft has implemented the PC/SC API as part of the Win32® API, which is the fundamental toolset for building Windows applications. Microsoft is also a member of the PC/SC Workgroup. your third question I did not understand. cheers, JJK _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
