1. 08 Apr, 2017 8 commits
  2. 03 Apr, 2017 1 commit
  3. 17 Mar, 2017 1 commit
  4. 05 Mar, 2017 1 commit
  5. 17 Feb, 2017 1 commit
  6. 04 Feb, 2017 1 commit
  7. 01 Feb, 2017 1 commit
  8. 29 Jan, 2017 1 commit
  9. 17 Jan, 2017 1 commit
  10. 02 Jan, 2017 1 commit
  11. 19 Dec, 2016 1 commit
  12. 06 Dec, 2016 1 commit
  13. 26 Nov, 2016 1 commit
  14. 20 Nov, 2016 1 commit
  15. 10 Nov, 2016 1 commit
  16. 31 Oct, 2016 1 commit
  17. 20 Oct, 2016 1 commit
  18. 19 Oct, 2016 1 commit
  19. 18 Sep, 2016 1 commit
  20. 05 Sep, 2016 1 commit
  21. 24 Aug, 2016 1 commit
  22. 29 Jul, 2016 3 commits
  23. 02 Jul, 2016 2 commits
  24. 27 Jun, 2016 1 commit
    • Ludovic Rousseau's avatar
      Handle "simultaneous" readers removal · b10d9dc1
      Ludovic Rousseau authored
      When a multi slot reader (say with 2 slots) is removed then
      SCardGetStatusChange() will return with .dwEventState bit
      SCARD_STATE_CHANGED set for the first slot. Then the present readers are
      enumerated again and the second slot may still be listed by pcscd at
      that time.
      
      But when SCardGetStatusChange() is called again then the second slot may
      have been removed by pcscd and SCardGetStatusChange() will fail and
      return SCARD_E_UNKNOWN_READER.
      
      This a toctou (Time of check to time of use) issue between
      SCardListReaders() call and SCardGetStatusChange() call.
      
      Before the change the command pcsc_scan just exited with an error
      message: SCardGetStatusChange: Unknown reader specified.
      
      No the readers are re-enumerated and the loop continues.
      b10d9dc1
  25. 10 Jun, 2016 1 commit
  26. 08 Jun, 2016 3 commits
  27. 19 May, 2016 2 commits