I am in the process of writing a system that reads from a JCOP smartcard with GP 2.2 and a custom applet on. All was going well, until I tried to do authentication, and I seem to have run into an issue. When ever I send an INITIALIZE UPDATE APDU to a card it always returns the same value back in the Card Challenge part of the response. It doesn't matter if I physically remove the card, when ever I call it I get the same values back. This behaviour is in correct as the Card Challenge part of the response should be (according to the spec) "an internally generated random number." When I run the APDUs through the native Windows PCSC layer I get randomness, but when I run it through pcsc-lite 1.8.8 in Open Suse there is no randomness. This is a problem as the applet on the card is secured, so in order to do anything, you need to be in an authenticated session and without the random Card Challenge all authentication fails. I have been using the same card and reader each time. Can anyone shed any light on this issue please?
-- View this message in context: http://musclecard.996296.n3.nabble.com/GP-2-2-INITIALIZE-UPDATE-0x50-oddness-tp5042.html Sent from the MuscleCard mailing list archive at Nabble.com. _______________________________________________ Muscle mailing list [email protected] http://lists.musclecard.com/mailman/listinfo/muscle_lists.musclecard.com
