Skip to content

Conversation

@frankmorgner
Copy link
Member

@frankmorgner frankmorgner commented Jan 30, 2020

  • If readers are attatched, the new reader is probed for a card to check
    if a notification needs to be sent
  • removal of readers are not notified to the user, we assume that PC/SC
    sends the correct card removal event
  • The list of readers to be monitored is adjusted once a reader (dis)appears
  • On macOS, without PnP notification, we always check for new/removed
    readers with SCardListReaders

fixes #1874

Checklist
  • macOS (Catalina)
  • Linux (Ubuntu 19.10)
  • Windows

@frankmorgner
Copy link
Member Author

macOS is working now.

Unfortunately, Windows has a high load after disconnecting a reader and I don't currently have the time to debug this...

@lgtm-com
Copy link

lgtm-com bot commented Mar 21, 2020

This pull request fixes 1 alert when merging 673d5d2 into d5ecafc - view on LGTM.com

fixed alerts:

  • 1 for FIXME comment

@lgtm-com
Copy link

lgtm-com bot commented Mar 21, 2020

This pull request fixes 1 alert when merging ed84e61 into d5ecafc - view on LGTM.com

fixed alerts:

  • 1 for FIXME comment

@lgtm-com
Copy link

lgtm-com bot commented Mar 27, 2020

This pull request fixes 1 alert when merging 584067a into 7840804 - view on LGTM.com

fixed alerts:

  • 1 for FIXME comment

@lgtm-com
Copy link

lgtm-com bot commented Mar 27, 2020

This pull request fixes 1 alert when merging 0803735 into 7840804 - view on LGTM.com

fixed alerts:

  • 1 for FIXME comment

@frankmorgner
Copy link
Member Author

I finally had time to test this across all platforms. It turns out, that there are more differences than I have initially thought. It also seems that sc_wait_for_event hasn't been tested anywhere else than in PKCS#11... Anyway, it all now looks good!

@lgtm-com
Copy link

lgtm-com bot commented Mar 27, 2020

This pull request fixes 1 alert when merging d6c75e3 into 7840804 - view on LGTM.com

fixed alerts:

  • 1 for FIXME comment

- If readers are attatched, the new reader is probed for a card to check
if a notification needs to be sent
- removal of readers are not notified to the user, we assume that PC/SC
sends the correct card removal event
- The list of readers to be monitored is adjusted once a reader (dis)appears
- On macOS, without PnP notification, we always check for new/removed
readers with SCardListReaders
- fixes interrupt handling in opensc-notify on Unix

fixes OpenSC#1874
@lgtm-com
Copy link

lgtm-com bot commented Mar 28, 2020

This pull request fixes 1 alert when merging 2901a2d into 7840804 - view on LGTM.com

fixed alerts:

  • 1 for FIXME comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

opensc-notify.exe(from OpenSC 0.20.0-rc2) - Win10( ver1809) - too high processor load

1 participant