Re: GP 2.2 INITIALIZE UPDATE (0x50) oddness

hello,

I have an idea, but to help me confirm it, can you post the response to the
SELECT APPLICATION command you send to the ISD?

Try 00A4 0400 00

BR

Sébastien Lorquet

Le 20/09/2013 09:46, landyman70 a écrit :
> Here is the 2 APDUs that get sent under linux:
> 80500300080102030405060708
> 00C000001C
> this yields:
> 611C [1C bytes waiting]
> 00020000000000000000030200528EDDBD4CFAE5179BF9E427D999A89000
> this breaks down into
> 00020000000000000000 - key diversification data
> 0302 - key information
> 0052 - sequence counter
> 8EDDBD4CFAE5 - card challenge
> 179BF9E427D999A8 - card cryptogram
> 9000 - result code (okay)
> And each time I execute these APDUs I get exactly the same result, where the
> card challenge section *should* be random.
> Under windows:
> 80500300080102030405060708
> 00C000001C
> yields:
> 611C
> 00020000000000000000030200267DAEA944AAA065ACCCB2C9654A059000
> breaks down into
> 00020000000000000000 - key diversification data
> 0302 - key information
> 0026 - sequence counter
> 7DAEA944AAA0 - card challenge
> 65ACCCB2C9654A05 - card cryptogram
> 9000 - okay
> when run multiple times, the sequence counter is incremented, and the card
> challenge and card cryptograms are different.
> Its the same reader and card each time.
> 
> 
> 
> --
> View this message in context: http://musclecard.996296.n3.nabble.com/GP-2-2-INITIALIZE-UPDATE-0x50-oddness-tp5042p5044.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
>