Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Omnikey 5025CL - 5325 compatibility mode activation #62

Closed
ghost opened this issue Oct 17, 2014 · 2 comments
Closed

Omnikey 5025CL - 5325 compatibility mode activation #62

ghost opened this issue Oct 17, 2014 · 2 comments
Assignees

Comments

@ghost
Copy link

ghost commented Oct 17, 2014

Implement native/compatible configuration for the 5025CL.

See doc 5025CL developer guide. Chapter 5.4.

@ghost ghost added the enhancement label Oct 17, 2014
@ghost ghost assigned Liryna Oct 17, 2014
@ghost
Copy link
Author

ghost commented Dec 2, 2014

Some updates:

The reader works in two modes: Default/Native (use CCID drivers) and Legacy (emulates an Omnikey 5325CL reader).

APDU to switch to legacy mode: FF 70 07 6B 07 A2 05 A1 03 8D 01 01 00 (need to be send with SCardTransmit)
APDU to revert to default mode (factory reset): FF 70 07 6B 09 A2 07 A1 05 A9 03 81 01 00 00 (need to be send with SCardControl)

Instead of switching to legacy mode to support the reader, we should implement the native mode and handle new ATRs.

_Legacy mode issue_
When switching to legacy mode, the latest drivers (v1.2.26.140) simulate the same ATR than in the native mode. Or it should simulate an Omnikey 5x25CL ATR. At the moment, Omnikey has reproduced the issue and is working on fixing it. Seems to be driver-related.

@Liryna
Copy link
Contributor

Liryna commented Dec 2, 2014

52bf650

@Liryna Liryna closed this as completed Dec 2, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant