GemaltoAccess TOP card: strange behaivior

View: New views
1 Messages — Rating Filter:   Alert me  

GemaltoAccess TOP card: strange behaivior

by Viktor TARASOV-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

have you ever seen the following card behavior, please?
With the card 'Gemalto Access TOP' or any other.

When trying to read the protected EF, without security condition satisfied,
the card answer contains the expected code error
(SC_ERROR_SECURITY_STATUS_NOT_SATISFIED)
but SW is preceded by 'Le' number of zeros.

According to ISO 7816-4 it's completely illegal - no data should be
returned when an error from 64xx to 6Fxx happens.

As it actually implemented in iso7816_read_binary() OpenSC procedure,
the error code is not checked if the data length is not zero.
And so, our application is quiet bewildered.


There are some logs:
...
2009-10-27 10:30:06
Outgoing APDU data [    5 bytes] =====================================
C0 B0 00 00 0F .....
======================================================================
2009-10-27 10:30:06 reader-pcsc.c:175:pcsc_internal_transmit: called
2009-10-27 10:30:06
Incoming APDU data [   17 bytes] =====================================
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 69 ...............i
82                                              .
======================================================================
2009-10-27 10:30:06 card.c:339:sc_unlock: called
2009-10-27 10:30:06 sc_unlock() locks 2
2009-10-27 10:30:06 Security status not satisfied


Kind wishes,
Viktor Tarasov.


--
Viktor Tarasov <viktor.tarasov@...>

_______________________________________________
opensc-user mailing list
opensc-user@...
http://www.opensc-project.org/mailman/listinfo/opensc-user