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

Backward protocol compatibility #199

Open
Erick555 opened this issue Aug 5, 2024 · 8 comments
Open

Backward protocol compatibility #199

Erick555 opened this issue Aug 5, 2024 · 8 comments
Assignees

Comments

@Erick555
Copy link

Erick555 commented Aug 5, 2024

Recently in 2.3.0 pcsc release there was minor protocol version bump. This was first protocol bump in 6 years.

This creates problem for using pcsc in containers (i.e. flatpak) where there's one client version but multiple server versions. Not updating client means all new servers are broken - updating means all old servers are. How to prevent such hopeless situation? Is it possible to introduce protocol negotiation instead of mismatch failure?

Alternatively is it possible to revert above commit until solution for protocol compat is found?

@LudovicRousseau
Copy link
Owner

Yes, it is a known issue.
See https://salsa.debian.org/rousseau/PCSC/-/issues/22

I do not use flatpack myself. So I have no motivation to implement something.

@LudovicRousseau
Copy link
Owner

I would love to work on a solution.

You can contact by by email. See https://blog.apdu.fr/articles/about_me/

@minosimo
Copy link

Hi, was SCardGetStatusChange() added at someone's request? Do you know of any applications making use of this command yet? I am trying to figure out whether it's safe to hold on 2.2.3.

@LudovicRousseau
Copy link
Owner

@minosimo SCardGetStatusChange() is part of the API since the beginning.

You can have a look at https://codesearch.debian.net/search?q=SCardGetStatusChange for some of its usage (626 results).

@minosimo
Copy link

Oh sorry, I copied the wrong string! It should have been GetReaderEvents().

@LudovicRousseau
Copy link
Owner

There is no GetReaderEvents in the source code. Maybe you mean CMD_GET_READER_EVENTS as listed in 53f57ed.

It has been added to solve the problem described in https://blog.apdu.fr/posts/2024/08/improved-scardgetstatuschange-for-pnpnotification-special-reader/

@inorton-entrust
Copy link

Hi Ludovic, I've run into this too, I have new-servers and a slightly older client. I appreciate this is a once-in-six-years thing.

Is it right to say that a newer client can talk to an older server, but an old client cannot talk to a new server?

@LudovicRousseau
Copy link
Owner

Is it right to say that a newer client can talk to an older server, but an old client cannot talk to a new server?

No.
You need to have the sever and the client using the exact same protocol version.

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

4 participants