1.5.3

• Retry reader init on any error, and do USB reset after repetitive init errors
• Update the bundled PC/SC-Lite from 2.0.0 to 2.1.0 (release notes for 2.0.1, release notes for 2.0.2, release notes for 2.0.3, release notes for 2.1.0)
  • SCardCancel() will return SCARD_S_SUCCESS even if the client already finished.
  • SCardConnect() & SCardReconnect() will now return SCARD_E_PROTO_MISMATCH if the application requests to use T=1 only but the reader supports T=0 only.
  • Fixed thread safety issues.

1.5.2

• Added support for the following readers:
  • AvidCard CAC Smart Card Reader.

1.5.1

• Fixed admin policy not being applied with some probability (#41).
• Allowlisted the following client applications:
  • Net iD client extension.

1.5.0

• Allowlisted the following client applications:
  • IDmelon Accesskey extension.
• Update Free CCID driver from 1.5.2 to 1.5.5 (release notes for 1.5.3, release notes for 1.5.4, release notes for 1.5.5).
  • Added support for the following readers:
    • ACS ACR1552 1S CL Reader
    • ACS ACR1552 CL Reader
    • ACS ACR1581
    • ACS ACR40T ICC Reader
    • ACS ACR40U ICC Reader
    • ACS WalletMate 1S CL Reader
    • Aktiv Rutoken SCR 3101 NFC Reader
    • Alpha-Project ANGARA Token
    • Broadcom Corp 58200 (idProduct: 0x5864)
    • Broadcom Corp 58200 (idProduct: 0x5865)
    • CIRIGHT ONE PASS U2F
    • Dexon Tecnologias Digitais LTDA eSmartDX
    • Excelsecu Card reader
    • GHI NC001
    • Identiv uTrust Token Flex
    • Imprivata USB CCID
    • KAPELSE eS-KAP-Ad
    • Kapelse inSide
    • KAPELSE KAP-Care
    • KAPELSE KAP-eCV
    • KAPELSE KAP-GO
    • KAPELSE KAP-LINK2
    • Kapelse KAP-Move
    • Kapelse Ti-Kap
    • rf IDEAS USB CCID
    • SIMHUB pcsc reader
    • SpringCard M519 with idProduct: 0x6212
    • SpringCard M519 with idProduct: 0x621A
    • WCMi SD5931

1.4.2

• Fixed the regression introduced in 1.4.0.
  • It manifested as random disconnections after a few hours of reader usage (#1097), slower card movement detection and occasional slot invisibility for multi-slot readers in the ChromeOS login setups.

1.4.1

• Fix crash/incorrect behavior in case of SCardConnect/Disconnect calls happening during the card insertion/removal (#1098).
• Minor logging improvements.

1.4.0

• Released support for Web Smart Card API.
  • The expose_chrome_smart_card_api policy, which temporarily gated this feature, is deprecated now. This functionality is on by default.
• Fix a possible crash in the USB subsystem.
• Minor logging improvements.
• Minor size reduction (-2%).

1.3.15.0

• Alpha implementation for Web Smart Card API (enable by setting the "expose_chrome_smart_card_api" policy to "True").
• UI for notifying the user in case the application crashed.

1.3.14.1

• Fix breakage on some composite readers like Rocketek (#849).
• Fix occasional crash on MAX_ATR_SIZE when Lock Screen is enabled (#840).
• Fix inability to self-restart after a crash (#823).
• Update PC/SC-Lite from 1.9.9 to 2.0.0 (release notes).
  • Reset eventCounter when a reader is removed.
  • Minor improvements.
• Improve the JavaScript API to allow obtaining the error code directly (#793).
• Require ChromeOS >= 81 (see #838 for motivation).
• Minor UI updates.

1.3.13.0

• Update Free CCID driver from 1.5.0 to 1.5.2 (release notes for 1.5.1, release notes for 1.5.2)
  • Added support for a few new devices.
  • Fix for an issue with AlcorMicro AU9560 and high-speed cards (see upstream's blog article).
  • Minor fixes.
• Update PC/SC-Lite from 1.9.8 to 1.9.9 (release notes).
  • Minor fixes (note: a few significant bugfixes from 1.9.9 had already been cherry-picked by us previously).
• Partial fix for Inbound transfer overflow USB issue.
  • (Note: Sometimes this error indicates a problem in the client application, not in the Smart Card Connector - see #136.)
• Fix incorrect type declarations in api.js.
  • The users of this library should pass data arrays as ArrayBuffer, not as arrays of bytes-numbers (see #805).
• Add warning logs when client application sends concurrent PC/SC calls (which is disallowed but "happens to mostly work" as of now).
  • WARNING for client application developers: If your application triggers these logs, please fix your application. In some future release, we'll tighten this check by forcing such requests be executed sequentially.
• Logging improvements:
  • Write logs to systemLog, when available (i.e., on ChromeOS >=111). It makes the logs automatically added to feedback reports. Also it makes the logs appear at chrome://device-log.
  • Remove misleading warning logs when unplugging a reader or switching to ChromeOS Lock Screen.