> I see that pcscd is always polling Capability 0x180, which is vendor defined.
> you want me to implement that capability ? what should it do ?
This was a backward compatible means of supporting multiple slots on a
reader - basically pcscd Set the Capability which was the slot. It's not
documented because I don't want anyone to use it - it was IFDHandler 1.0
> (for cleanup only) i see the atr debugging output not only when the
> atr is read via power_up, but also at different times. do you parse
> the atr more than once ?
The atr is probably parsed during SCardConnect also.
>
> icc events: i don't know how to get a notification from usb for devices
> removed or added. but if i knew, how would i tell pcsc ?
You don't - pcscd does this for you. I sent you the Info.plist
information last night, your device will be identified by vendor/product
ID.
>
> how can i support several tokens at the same time ?
> might be usefull (for example format token 1, create key, create certifikate,
> use token 2 to sign the certifikate, save signed certifikate on token 1).
Lun - logical unit number. Read the IFD Handler documentation in the
ifd-devkit.
>
> documentation: i found the pcsc specification very usefull. part 3
> is the ifd handler, and part 2 has T=0 and T=1 protocol.
>
> ifd-devkit:
> why don't you licence the skeleton as public domain ?
> anyway i don't need it and don't use it:
> - header files are in pcsc-lite
> - the documentation available on your website
> - writing the skeleton and a makefile is no work.
Last time I checked BSD was a public domain license.
from ifd-devkit-1.0.0/LICENSE
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software
must display the following acknowledgement:
This product includes software developed by:
David Corcoran <[EMAIL PROTECTED]>
http://www.linuxnet.com (MUSCLE)
4. The name of the author may not be used to endorse or promote products
derived from this software without specific prior written permission.
>
> ifd-test:
> i looked at it. but it seems to be for a smartcard reader ?
> i.e. you need to have these cards ? i'm writing a token driver,
> so i'm not sure if this helps me.
probably not. That kit uses the PC/SC test suite of smartcards.
> website/drivers:
> scm301 doesn't come in object form, its in source code.
only public domain portions are in source form. you will find object
code in that driver.
>
> bundle:
> so a bunle is a directory tree like this:
> somename.bundle/
> somename.bundle/Contents/
> somename.bundle/Contents/Info.plist xml file
> somename.bundle/Contents/Linux/
> somename.bundle/Contents/MacOS/
> somename.bundle/Contents/Resources/
>
> and the library is simply but in the Linux directory, with the name
> entered in the key CFBundleExecutable ?
> the idea is fine, and it only tries to look like xml, but isn't.
> and it's complex. couldn't this be easier ?
Bundles are widely used on Mac OS X. I want to provide portability.
> so much for now. i don't know what i need to do to support T=0 in a
> driver. my usb capture shows how the windows driver uses T=1, and i
> doubt that a character based protocol over usb is usefull.
> i found that opensc always uses T=0 and modified it to request ANY
> protocol. what is the meaning of 0xff as return value for active protocol?
0xFF means Error. Look at pcsclite.h for protocol information.
About T=0/1 - you will have to write this if your token does not do this.
but if your token does not use T=0, then why write a T=0 stack ? You can
make a fake ATR for your token, and not use T=0.
Dave
***************************************************************
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
***************************************************************
