Bug#890126: libccid: C3PO LTC32 v2 doesn't work well when the PIN number of a card is required

2018-02-11 Thread Robert Marsellés
Hello,

>>
>>     5) Additional info
>>  The discussion with the Belgium help desk service
>>   (serviced...@fedict.be) and the logs (generated by the
>>  software supporting their card -- attached file) suggest that
>>  there is a problem with the the firmware. Specifically:
>>
>>  "It would appear there is a firmware problem with this
>> cardreader.
>>  The reader is shown as having a pin pad, even though it doesn't.
>>  Therefore it is sent instructions it can't handle."
> 
> Belgium help desk service is right. I fixed the problem 3 weeks ago in
> the upstream source code.
> https://salsa.debian.org/rousseau/CCID/commit/a27a11711a9861acea3a9b43bba56ba157c670af
> 
> 
> It may be time to make a new libccid release to fix this problem.
> 

That's fast. Thank you very much. If I can be of any assistance, let me
know.

robert



Bug#890126: libccid: C3PO LTC32 v2 doesn't work well when the PIN number of a card is required

2018-02-11 Thread Ludovic Rousseau

Le 11/02/2018 à 13:06, robert a écrit :

Package: libccid
Version: 1.4.28-2
Severity: important

Dear Maintainer,


Hello,


1) What led up to the situation?
 Trying to use the card reader with the Belgium ID card
 to access the Belgium online services for the citizens.
 (http://www.ibz.rrn.fgov.be/fr/registre-national/mon-dossier/).

2) What exactly did you do (or not do) that was effective (or
  ineffective)?
 The reader works with the Spanish ID card but no PIN is
 required (at least in the web sites I used it before such
  as https://www.sedecatastro.gob.es/).

 The BeID card is recognised by pcsd_scan. When trying to
 access the Belgium online services, a window pops up showing
 the information of the card.

3) What was the outcome of this action?
 Agreeing with the showed identifiying device (BeID card)
 yields an "secure connection failed" error.

4) What outcome did you expect instead?
 Access to the Belgium citizen online services.

5) Additional info
 The discussion with the Belgium help desk service
  (serviced...@fedict.be) and the logs (generated by the
 software supporting their card -- attached file) suggest that
 there is a problem with the the firmware. Specifically:

 "It would appear there is a firmware problem with this cardreader.
 The reader is shown as having a pin pad, even though it doesn't.
 Therefore it is sent instructions it can't handle."


Belgium help desk service is right. I fixed the problem 3 weeks ago in the 
upstream source code.
https://salsa.debian.org/rousseau/CCID/commit/a27a11711a9861acea3a9b43bba56ba157c670af

It may be time to make a new libccid release to fix this problem.

Thanks

--
 Dr. Ludovic Rousseau



Bug#890126: libccid: C3PO LTC32 v2 doesn't work well when the PIN number of a card is required

2018-02-11 Thread robert
Package: libccid
Version: 1.4.28-2
Severity: important

Dear Maintainer,

   1) What led up to the situation?
Trying to use the card reader with the Belgium ID card
to access the Belgium online services for the citizens.
(http://www.ibz.rrn.fgov.be/fr/registre-national/mon-dossier/).

   2) What exactly did you do (or not do) that was effective (or
 ineffective)?
The reader works with the Spanish ID card but no PIN is
required (at least in the web sites I used it before such
 as https://www.sedecatastro.gob.es/).

The BeID card is recognised by pcsd_scan. When trying to
access the Belgium online services, a window pops up showing
the information of the card.

   3) What was the outcome of this action?
Agreeing with the showed identifiying device (BeID card)
yields an "secure connection failed" error.

   4) What outcome did you expect instead?
Access to the Belgium citizen online services.

   5) Additional info
The discussion with the Belgium help desk service
 (serviced...@fedict.be) and the logs (generated by the
software supporting their card -- attached file) suggest that
there is a problem with the the firmware. Specifically:

"It would appear there is a firmware problem with this cardreader.
The reader is shown as having a pin pad, even though it doesn't.
Therefore it is sent instructions it can't handle."




-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_ES:ca (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libccid depends on:
ii  libc6 2.26-4
ii  libusb-1.0-0  2:1.0.21-2

libccid recommends no packages.

Versions of packages libccid suggests:
pn  pcmciautils  

-- no debconf information
2018-01-14 12:44:48 - 11246|14428402432 - cardlayer - ERROR: pinpad reader 
returned 

2018-01-14 12:44:48 - 11246|14428402432 - cardlayer - ERROR: Only 0 byte(s) 
returned from the card
2018-01-14 12:52:19 - 11246|14428402432 - cardlayer - ERROR: pinpad reader 
returned 

2018-01-14 12:52:19 - 11246|14428402432 - cardlayer - ERROR: Only 0 byte(s) 
returned from the card
2018-01-14 13:00:00 - 11246|14428402432 - cardlayer - ERROR: pinpad reader 
returned 

2018-01-14 13:00:00 - 11246|14428402432 - cardlayer - ERROR: Only 0 byte(s) 
returned from the card
2018-01-14 13:02:53 - 11246|14428402432 - cardlayer - ERROR: pinpad reader 
returned 

2018-01-14 13:02:53 - 11246|14428402432 - cardlayer - ERROR: Only 0 byte(s) 
returned from the card
2018-01-17 18:40:17 - 4232|140655001970432 - cardlayer - ERROR: pinpad reader 
returned 

2018-01-17 18:40:17 - 4232|140655001970432 - cardlayer - ERROR: Only 0 byte(s) 
returned from the card
2018-01-17 19:59:15 - 4232|140655001970432 - cardlayer - ERROR: pinpad reader 
returned 

2018-01-17 19:59:15 - 4232|140655001970432 - cardlayer - ERROR: Only 0 byte(s) 
returned from the card
2018-01-17 19:59:18 - 4232|140655001970432 - cardlayer - ERROR: pinpad reader 
returned 

2018-01-17 19:59:18 - 4232|140655001970432 - cardlayer - ERROR: Only 0 byte(s) 
returned from the card
2018-01-17 20:00:53 - 5266|140225292379904 - cardlayer - ERROR: pinpad reader 
returned 

2018-01-17 20:00:53 - 5266|140225292379904 - cardlayer - ERROR: Only 0 byte(s) 
returned from the card
2018-01-18 18:56:25 - 4005|139719170959104 - cardlayer - ERROR: pinpad reader 
returned 

2018-01-18 18:56:25 - 4005|139719170959104 - cardlayer - ERROR: Only 0 byte(s) 
returned from the card
2018-01-21 17:07:03 - 2840|140356325582592 - cardlayer - ERROR: pinpad reader 
returned 

2018-01-21 17:07:03 - 2840|140356325582592 - cardlayer - ERROR: Only 0 byte(s) 
returned from the card
2018-01-21 17:07:13 - 2840|140356325582592 - cardlayer - ERROR: pinpad reader 
returned 

2018-01-21 17:07:13 - 2840|140356325582592 - cardlayer - ERROR: Only 0 byte(s) 
returned from the card
2018-01-21 17:07:17 - 2840|140356325582592 - cardlayer - ERROR: pinpad reader 
returned 

2018-01-21 17:07:17 - 2840|140356325582592 - cardlayer - ERROR: Only 0 byte(s) 
returned from the card
2018-01-21 17:07:19 - 2840|140356325582592 - cardlayer - ERROR: pinpad reader 
returned 

2018-01-21 17:07:19 - 2840|140356325582592 - cardlayer - ERROR: Only 0 byte(s) 
returned from the card
2018-01-21 17:07:31 - 2840|140356325582592 - cardlayer - ERROR: pinpad reader 
returned 

2018-01-21 17:07:31 - 2840|140356325582592 - cardlayer - ERROR: Only 0 byte(s) 
returned from the card
2018-01-24 21:07:43 - 4699|140576003258112 - cardlayer - ERROR: pinpad reader 
returned 

2018-01-24 21:07:43 - 4699|140576003258112 - cardlayer - ERROR: Only 0 byte(s) 
returned