Hello. I've tested the patch, it fixes the issue, but only for tokens with firmware 0.12 It appears that one of my tokens has firmware 0.13 and it is still affected by the bug. Adding 0x0013 to the condition also fixes 0.13 tokens.
> tags 993647 upstream fixed-upstream pending > thank > > Le 06/09/2021 à 12:16, Vladimir K a écrit : > >> Hello. > > Hello, > >> safenetauthenticationclient maintains some sort of binary cache in >> /var/tmp/eToken.cache/. >> It masks the problem after libccid upgrae for a while. >> I was able to fully reproduce it on a fresh test eToken 5110, the problem >> appears after the cache is cleared. >> >> 3 logs of pcscd attached: >> 1. with libccid 1.4.35, success >> 2. with libccid 1.4.36, just after upgrade, success >> 3. with libccid 1.4.36, after cleaning SAC cache, fail. >> >> Each log is gathered while the following actions were performed: >> 1. connected token. >> 2. run p11tool --login --list-all 'pkcs11:token=Test%20Token', entered PIN >> 3. disconnected token > > Thanks for the logs. > > I fixed the issue upstream in > https://salsa.debian.org/rousseau/CCID/-/commit/b48e1e697010431b7f03d4ecfe917ceee95e2c64 > > I have no idea when I will make a new upstream release of the CCID driver. > In the mean time I propose you to apply the fix and rebuild the driver > yourself. > > Bye > > -- > Dr. Ludovic Rousseau
