Jan,
Many thanks for your response - also all the others -
many thanks.
I agree that the error status indicates the length of
the APDU to wrong. However, the APDU in question that
is generated in the example code starts with the bytes
[00 08 00 00 1B 1B bytes]. I already verified the
APDU size
Bitter experience is showing that card software (OS) developers are treating
ISO 7816-4 as a smorgasbord, choosing what they want to implement, and even
choosing which parts of a command definition to implement. Towards the end
of 7816-4, in the area of optional methods for a card to indicate
Unsubscribe please.
***
Linux Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/smartcard/index.html
***
office:
Holger Meureremail: [EMAIL PROTECTED]
AUCOS elektronische Ger"ate GmbH
Matthiashofstr. 47-49Phone: +49-241-44664-176
D-52064 Aachen Fax: +49-241-44664-99
-- Forwarded message --
Date:
Hello all:
I'm writing PAM modules for smartcard support. Got
it working on Linux, but I'm having compile errors with Solaris.
I am attempting to get pcsc-lite compiling on Solaris 8.
I'm using gcc 2.95.2 and I've tried pcsc-lite 0.7.8 to 0.8.9.
All return the same errors:
sys_unix.c: In
hi,
if you have some time have a look at 'fernando.llobregat.free.fr' i have
placed there the actual state of the skam tool.
It has been tested on a linux mandrake 7.1, needs KDE2.1 and pcsc to be
installed in /usr/local/pcsc.
Besides the apdu manager i have also done a KControl module to
Hi,
Actually you can remove in readerfactory.c starting from:
/* Attempt a passive lock on the shared memory file */
..
..
SYS_Exit(1);
}
It is only so pcscd can see if other pcscd's are running and give an error
message. Cut that code block out and then remove SYS_Lock from
