Bug #302
closed
internal error with "Basisleser"
Added by Marcel Selhorst almost 10 years ago.
Updated over 9 years ago.
Description
When using OpeneCardApp (versions 1.0.4 or 1.0.5) under Linux with a ReinerSCT "Basisleser", we receive an internal error when performing eID.
When using a ReinerSCT "Komfortleser", everything works fine.
We tested two services: sign-me (with alternative activation) and Deutsche Rente (with plugin activation) with the same results.
Please find attached the logfiles for Basis and Komfort when used with sign-me.
Note: With the official AusweisApp in both combinations ("Basis" and "Komfort"), we have no issues.
Files
- Status changed from New to In Progress
- Assignee changed from Tobias Wich to Hans-Martin Haase
We believe to have found the problem in the routine reading EFCardSecurity. Need further investigation to be sure.
- Status changed from In Progress to Feedback
After all we clould not find the problem. We suspect that the problem got fixed with the recent changes in PACE and EAC.
Please confirm if the problem went away.
Hi,
I couldn't reproduce this issue due to issue #306, as I get a lot of TCToken retrieval exceptions.
However, on the KBA page, I can use the Komfort-Reader, but not the Basis-Reader.
Can you reproduce this?
I successfully requested my list of traffic offenses at KBA today using v1.1 of the Open eCard App (with legacy activator) under Windows 7 using a "Basisleser".
Hence this problem at least does not seem to be existing on windows.
I had a similar Problem with 1.1.0-rc with the Reiner SCT Basisleser under Ubuntu. There the EFCardSecurity was too short, ~200 Bytes at the end were missing. This problem does not occur in 1.1.0-rc2 any more.
- Status changed from Feedback to Closed
Hauke Mehrtens wrote:
I had a similar Problem with 1.1.0-rc with the Reiner SCT Basisleser under Ubuntu. There the EFCardSecurity was too short, ~200 Bytes at the end were missing. This problem does not occur in 1.1.0-rc2 any more.
This is great news as it means this problem was caused by the wrong read routine used for EFCardSecurity. The standard reader performs this task by itself so this is obviously not a problem there.
Conclusion: fixed in 559fc708e1d
Also available in: Atom
PDF