Bug #370
closedconnect()-failure after removing and again providing card
0%
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
Updated by Tobias Wich almost 10 years ago
Please try this again with the version on https://jnlp-dev.openecard.org
Updated by Hans-Martin Haase almost 10 years ago
- Status changed from New to Feedback
Updated by Detlef Hühnlein over 9 years ago
- File richclient_info.log richclient_info.log added
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.
Updated by Tobias Wich over 9 years ago
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?
Updated by Detlef Hühnlein over 9 years ago
- File richclient_info-unknown-error-0x458.log richclient_info-unknown-error-0x458.log added
- File richclient_info-v2.log richclient_info-v2.log added
- File richclient_info-v3.log richclient_info-v3.log added
- File d-trust-message.PNG d-trust-message.PNG added
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).