Changes between Version 21 and Version 22 of LeopardBugs

Show
Ignore:
Timestamp:
06/04/09 06:59:25 (15 months ago)
Author:
ludovic
Comment:

update list of bugs

Legend:

Unmodified
Added
Removed
Modified
  • LeopardBugs

    v21 v22  
    44 
    55'''December 2008 update:''' Please upgrade to Mac OS X 10.5.6, available via Software Update. It includes the [http://pcsclite.alioth.debian.org/ccid.html open source CCID library v1.3.8] and fixes at least some of the problems listed here. 
    6  
    7 == ATR reporting error (1) == 
    8  * '''Description'''  
    9 The ATR reported for example by {{{/Library/OpenSC/bin/opensc-tool --atr}}} (doing it a least twice because sometimes, at the first run the ATR is correctly reported...) is appended by 0x00. This intereferes with the card type recognition. 
    10  
    11 You can also use the Mac OS X tool {{{pcsctest}}} to display the card ATR. The result is the same and does not involve any OpenSC program. 
    12  *  '''Problem ID''' 
    13 5757100, 5485550, 5479263 
    14  * '''Workaround''' 
    15  1. Use the last version of [http://www.opensc-project.org/files/sca/experimental/ experimental] SCA.[[BR]]OR 
    16  
    17  2. Create an entry in {{{/Library/OpenSC/etc/opensc.conf}}} with something like this: 
    18 {{{ 
    19 card_atr 3B:7D:11:00:00...... { 
    20     driver = your_card_driver 
    21     type = value 
    22     } 
    23 }}} 
    24 Sometimes you need to define a type too. Check for your card in  
    25 [http://www.opensc-project.org/opensc/browser/trunk/src/libopensc/cards.h this file] to get this value. 
    266 
    277== ATR reporting error (2) == 
     
    3717== Pcscd choose a bad communication protocol == 
    3818 * '''Description'''  
    39 For some card, the card requests T=0 protocol for communicating, and pcscd uses T=1. This is documented with SetCOS 4.4.1 (ATR: 3B 9F 94 80 1F C3 00 68 11 44 05 01 46 49 53 45 31 C8 07 90 00 19). With some readers (ACR38U), the card simply doesn't answer to any APDU. 
     19Cards declaring T=0 and T=15 protocols will be configured by pcscd as T=1. This is documented with SetCOS 4.4.1 (ATR: 3B 9F 94 80 1F C3 00 68 11 44 05 01 46 49 53 45 31 C8 07 90 00 19). With some readers (ACR38U), the card simply doesn't answer to any APDU. 
    4020 *  '''Problem ID''' 
    41 5757076 
     215757076, 6920676 
    4222 * '''Workaround''' 
    4323None 
    44  
    45 == Pcscd choose a bad communication protocol == 
    46  * '''Description'''  
    47 For some card pcscd uses the wrong prorocol. Bug reported in http://lists.apple.com/archives/Apple-cdsa/2008/Mar/msg00017.html with a GemPC Twin USB and an Aladdin eToken Pro card (ATR: 3B F2 18 00 02 C1 0A 31 FE 58 C8 09 75). {{{pcsctest}}} returns {{{Testing SCardConnect : Card protocol mismatch.}}} 
    48  *  '''Problem ID''' 
    49 5818373 
    50  * '''Workaround''' 
    51 Install a working driver like this CCID driver http://pcsclite.alioth.debian.org/ccid.html#MacOSX 
    5224 
    5325== Token unlock in !KeyChainAccess == 
     
    142114None 
    143115 
    144 == SCardControl() does not work with a buffer length > 264 bytes == 
    145  * '''Description'''  
    146 It is not possible to use the SCardControl() function with a receive buffer larger than 264 bytes. 264 bytes (MAX_BUFFER_SIZE) is the maximum size for an normal APDU. 
    147  *  '''Problem ID''' 
    148 5962937 
    149  * '''Workaround''' 
    150 Use buffers not larger than 264 bytes. No use of "extended APDU" size buffers. 
    151  
    152116== PC/SC never returns the warm ATR of a dual-ATR card == 
    153117 * '''Description'''