Bug #370
closed
connect()-failure after removing and again providing card
Added by Detlef Hühnlein over 9 years ago.
Updated about 9 years ago.
Description
After removing and again providing a signature card there is a connect() failure.
There are also some sharing violations in the log, which might contribute to the
problem.
Files
- Status changed from New to Feedback
The removal and again inserting of the card seems to be fixed. The TLS-authentication at skidentity.de/service with VR-BankCard works fine.
However there seems to be a problem with the D-Trust-card. See attached log.
However there seems to be a problem with the D-Trust-card. See attached log.
Is this a problem related to this issue, or is it a general problem with the D-Trust card?
It seems to be a specific problem with the D-Trust-card. Nevertheless we should have a look at it to
understand the strange behaviour.
In the integrated reader there is an "unknown PC/SC error 0x458" (see ...error-0x458.log),
in the CyberJack wave there is a strange message "cyberJack Firewall - Kartenbefehl wird zur Sicherheit blockiert!" and
the app shows an error that it can not contact the card in an exclusive mode (see ...-v3.log and d-trust-message.PNG).
- Status changed from Feedback to Closed
Also available in: Atom
PDF
