Re: [Opensc-devel] opensc-0.18.0-rc1 tests with MyEID card

[Peter P. <pop...@gm...>]

Hi,

On Mon, Apr 23, 2018 at 12:32 PM, Frank Morgner <fra...@gm...>
wrote:



> I have no idea what could go wrong with the change you've pointed out.
> Does certutil.exe work as expected (note that the output of the tool may
> also indicate some problem)? certutil uses both, authentication and
> signature key (and PIN). Could you send a debug log of both cases?
>
>

If I run certutil -v -scinfo  with  opensc from apveyor 0.17.0.1461  or
0.17.0.1462, result is same (identical lines in CMD window). The test card
contains one certificate, certutil -scinfo can import this cert (there is
2x PIN dialog before certificate is available for import) Only EDGE browser
fails .. PIN dialog is not displayed (version 0.17.0.1462, same in
opensc-0.18.0-rc1).

Version 0.17.0.1461 is working, normal PIN dialog is displayed in EDGE...


Here cases what EDGE display in small window after connect to site that
need TLS client auth (for 0.17.0.1462, same in 0.18.0-rc1) :

1. no smart card in reader - EDGE window "Connect a smart card"
2. different smart card (with diffent keys/certificates" EDGE window
"Checking status"
     and some moment later "The smart card cannot perform the requested
operation or the operation requires a different smartcard"
3. after inserting correct smart card EDGE window "The smart card is ready
for use" I can push "OK" button now, but no PIN is requested, connect to
site fails

It is possilble that EDGE request this pin from PIN-Pad and, because I do
not have reader with PIN-Pad  this  pin requester fails ? I'm no familiar
with the windows API...


There is small difference certutil -v -scinfo (maybe importatnt) in
0.18.0-rc1 and 0.17.0.1462 ..  I am prompted for PIN (2x) and then I can
check certificate details, and install certificate.. In both versions
certificate is installed and import reports no error, but, in 0.18.0-rc1
there are several lines in cmd window:

P:2660 T:7408 2018-04-23 14:45;04:01 Cannot connect card in reader 'Generic
EMV Smartcard Reader 0'
(Tomorrow I will try to find out which version is first affected with this
problem)



Peter