From fsaavedr at dcc.uchile.cl  Thu Dec  1 05:19:57 2022
From: fsaavedr at dcc.uchile.cl (Felipe Saavedra)
Date: Thu, 1 Dec 2022 10:19:57 -0300
Subject: [Pcsclite-muscle] Need some pointers/help wiegand readers
Message-ID: <fd6fb12b-9197-a96d-568f-33d6f113a17c@dcc.uchile.cl>

Hi Everyone,

I'm Felipe. I just started to develop a code to interact with a wiegand
reader on cpp with an interface for nodejs. I am trying to get a
functionality like node-pcsclite, but I am getting a lot of questions
while reading the code internals and the interaction with pcsc-lite.

First, i was trying to find some pointers in the interaction with pcsc
and the wiegand protocol and if any of you have worked in some alike
proyect. If so, can you help me with some pointers?

If the later answer is negative, with your knowledge, do you think it is
possible?

Best Regards,

Felipe Saavedra



From ludovic.rousseau at gmail.com  Sat Dec 17 02:43:14 2022
From: ludovic.rousseau at gmail.com (Ludovic Rousseau)
Date: Sat, 17 Dec 2022 11:43:14 +0100
Subject: [Pcsclite-muscle] AlcorMicro AU9560 reader and fast smart cards:
 help from crowd needed
Message-ID: <CAGstE8AH+6TXKCQSQGUnqvJDXxKiqknu-B7o6gvgFCO2AZvgHw@mail.gmail.com>

Hello,

The AlcorMicro 9560 smart card reader has problems with high speed smart cards.
The card must have a TA1 > 0x95.

If you have this combination of reader + card then you can help me.
See my blog article for more details.
https://ludovicrousseau.blogspot.com/2022/12/alcormicro-au9560-reader-and-fast-smart.html

Thanks

--
 Dr. Ludovic Rousseau


From f.dumas at ellis.siteparc.fr  Fri Dec 30 05:35:03 2022
From: f.dumas at ellis.siteparc.fr (Frederic Dumas)
Date: Fri, 30 Dec 2022 15:35:03 +0200
Subject: [Pcsclite-muscle] SCR333v1 - STCII DFU Adapter - firmware update
Message-ID: <8F22D74A-5899-476A-82CA-77A7D740293E@ellis.siteparc.fr>


Hello everyone on the mailing list,

Ludovic invited me to ask my question to the members of this list. It is about the SCR333 card reader, from SCM Microsystems (the company has now become Identiv by merger-acquisition). This hardware, although perfectly compatible with the current standards, is considered "obsolete" by its manufacturer, who therefore no longer offers support for it.

One of these card readers [1], and a few months later a second, advertised themselves as "STCII DFU Adapter" on the USB bus, and became inaccessible through CCID. The matter is identified in the manufacturer's documentation [2]; it would be enough to reflash the reader with the original firmware to fix it.

On its website, the manufacturer no longer provides the firmware. Its online technical support is also unable to find a copy of this firmware.


Does any of you on the list have the SCM's firmware for the SCR333 card reader in your archives?


The Common Access Card web page [3], maintained by a retired US military man, offers firmware for the SCR331 model and another for the SCR3310 model, available for download. Thanks to a nice guy at Cardlogix for redirecting me to this resource.

Do either of these two readers share the same PCB with the SCR333 (i.e. the same firmware)?


More out of curiosity, but also a bit for practical purposes, does anyone also know what the trigger might be that causes the firmware to "corrupt"? Could an electrostatic shock have altered the flash memory of the STC microcontroller? Or would the old firmware versions be sensitive to a magic word that they see passing over the USB bus? Without understanding the cause, I could only observe that "suddenly" one or the other drive was no longer seen as a CCID device.

Thanks in advance for any advice!


Fr?d?ric

[1] SCR333 V1 ; the PCB reads: rev 1.1 12 DEC 2002
[2] Smartcard Reader - Installation & Troubleshooting Manual - Version 1.0 - November 17, 2008, p.17
[3] https://militarycac.org/cacdrivers.htm

--
Fr?d?ric Dumas
f.dumas at ellis.siteparc.fr







