EID-MW 4.1.21v4.1.21-0xenial1 stops working if no id-card is initially present

[Bernard Decock]

I received an update of the middle ware ( version 4.1.21v4.1.21-0xenial1 ). Card-reader = Digipass by Vasco. Card-reader and middle ware was working fine before this update.

Observations
1. Start computer and log in
2. connect eid-card-reader => Green power-led switches on, but extinguishes after a short time => Card-reader isn't working any longer

Work around
1. Start computer and log in
2. Put id-card into reader and connect then the reader to the computer => card-reader starts working normally.

As soon as step 2 was successful, one can remove the reader and plug back in.

OS = Linux Mint Cinnamon 18.1
Kernel = 4.8.0.32-generic

[Bernard Decock]

Op maandag 26 december 2016 09:41:33 UTC+1 schreef Bernard Decock:

I received an update of the middle ware ( version 4.1.21v4.1.21-0xenial1 ). Card-reader = Digipass by Vasco. Card-reader and middle ware was working fine before this update.

Observations
1. Start computer and log in
2. connect eid-card-reader => Green power-led switches on, but extinguishes after a short time => Card-reader isn't working any longer

Work around

1. Log off and log in

[Bernard Decock]

Op maandag 26 december 2016 09:41:33 UTC+1 schreef Bernard Decock:

I received an update of the middle ware ( version 4.1.21v4.1.21-0xenial1 ). Card-reader = Digipass by Vasco. Card-reader and middle ware was working fine before this update.

Another observation. After installing

sudo apt install pcsc-tools

, when you start

pcsc_scan

before one connects the reader, the reader starts working ok (Powerled remains on)

 

[Wouter Verhelst]

Hi Bernard,

Sorry about the late reply, I was on holiday.

On 26-12-16 09:41, Bernard Decock wrote:
> I received an update of the middle ware ( version 4.1.21v4.1.21-0xenial1
> ). Card-reader = Digipass by Vasco.

Given the below, I suspect this is a Digipass 905. Can you confirm?

> Card-reader and middle ware was
> working fine before this update.
>
> Observations
> 1. Start computer and log in
> 2. connect eid-card-reader => Green power-led switches on, but
> extinguishes after a short time => Card-reader isn't working any longer
>
> Work around
> 1. Start computer and log in
> 2. Put id-card into reader and connect then the reader to the computer
> => card-reader starts working normally.

There is a known issue (firmware bug) with the v1.1 firmware of the
digipass 905, which may enter into a nonrecoverable suspend state. The
symptoms are exactly as you describe, so I suspect you're hitting that
problem.

Since this is a firmware bug, there is nothing we can do about it. For
more information, please see this page by vasco about the issue:

https://retail.vasco.com/install/faq/20100114_990081.aspx

--
Wouter Verhelst

[Bernard Decock]

Op woensdag 4 januari 2017 10:13:52 UTC+1 schreef Wouter Verhelst:

Hi Bernard,

Sorry about the late reply, I was on holiday.

On 26-12-16 09:41, Bernard Decock wrote:
> I received an update of the middle ware ( version 4.1.21v4.1.21-0xenial1
> ). Card-reader = Digipass by Vasco.

Given the below, I suspect this is a Digipass 905. Can you confirm?

Reader = VASCO DP905v1.1 00 00

Hi Wouter, I'm aware of this firmware-bug, as I posted a problem for this reader in 2014 : https://groups.google.com/forum/#!topic/eid-mw/xCmQ9q0Vx3g . The strange thing was that I encountered that problem after logging in and then connecting the reader. I had this issue on 2 computers. For the moment, I don't understand what caused this issue, everything is working fine. The only thing is can see that when the screen locks after a timeout, that then the powerled = off (which is of course normal). If you log in and want to connect the reader again, the power-led goes on for a while (this looks as the firmware-bug). You can only recover from this state either by putting your id-card into the reader and then plug them in or by starting pcsc-scan. If pcsc-scan is running, then when the reader is plugged in, the power-led remains on. Anyhow I don't encounter the problem stated earlier any longer, although I don't understand what caused precisely caused the reader to behave "normally" again.