Hi David any everyone.

I see that pcscd is always polling Capability 0x180, which is vendor defined.
you want me to implement that capability ? what should it do ?

(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 ?

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 ?

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).

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.

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.

website/middleware:
the url and version of OpenSC changed.

website/drivers:
scm301 doesn't come in object form, its in source code.

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 ?

for example pcscd could simple go thru all files in the hotplug
directory, try to load them as driver and query the capabitlities.
all informations now in the file should be available as capability
or could be added as vendor defined capability. pcscd can then
power on the driver, close the channel, unload the library, load
it again later, etc.

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?

as always, thanks for your help.

regards, andreas

***************************************************************
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 majordomolinuxnet.com with
unsubscribe sclinux
***************************************************************

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]