On 27/06/06, michel memeteau <[EMAIL PROTECTED]> wrote:
Hi all , I was wondering about general PCSC/windows issues and if those
functionnalities are present in PCSC-lite.
After digging in the mailing list archive ( and the one from microsoft
smardcard), I could not get a clear status.
Using a PCSC API, we try :
Sending a PPS request using the PCSC API :
It seems that this features is only available through proprietary
commands spécific to a driver, or are disable for security issues if sended
as through ScardTransmit ( results sw1sw2=6982 : the system denies
processing of any further commands due to security reason)
The PC/SC application can only select the protocol to use (T=0 or
T=1). The driver then decides what to do for the PPS.
In my CCID driver [1] the PPS exchange is done by the driver or by the
reader depending on the reader firmware capabilities.
Changing the Vcc Voltage : This feature is available at the reader driver
level at PowerOn. I did not find a way even proprietary to specify through
ScardReconnect a specific Vcc.
You can't do that using a documented API.
But you can do whatever you want if the application directly talks to
the driver using SCardControl(). It is then "proprietary" commands
only supported by this particular driver.
In my CCID driver you can change the Vcc to use by editing the
Info.plist configuration file and changing ifdDriverOptions:
bits 4 & 5: (values 0, 16, 32, 48)
0: power on the card at 5V (default value)
16: power on the card at 3V and then, it 3V fails use 5V
32: power on the card at 1.8V, then 3V and then 5V
48: let the reader decide
I did not try with the windows Pcsc-lite API, but I would if a solution
would came out using it.
You should get the (full) documentation of your reader driver. It may
already support a lot of SCardControl() commands.
Bye,
[1] http://pcsclite.alioth.debian.org/ccid.html
--
Dr. Ludovic Rousseau
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle
