Public transport cards are going PKI In a previous article, we introduced the MIFARE DESFire DuoX in its VDE EV configuration for secure e-mobility services. That demo illustrated a broader trend: asymmetric cryptography schemes are gaining ground over symmetric schemes. With ECC now fully mature, and silicon costs low enough to run ECDSA and/or ECDH … Read more
Why EV charging security matters The electric vehicle (EV) revolution is underway — and in Europe, it’s accelerating fast. With ambitious targets for phasing out internal combustion engines, EV charging infrastructure is booming. But more charging stations means more opportunities for frauds and cyberattacks. For too long, many EV-charging systems have relied on nothing more … Read more
Today we’re going to offer you an article that’s a little different from our usual fare, since it’s less about going into the details of how to implement a SpringCard product than about presenting a small piece of software that can help you discover the world of NFC and contactless smart cards.
It’s called NFC Tools, and has been developed by Wakdev.
SpringCard Puck family products can be used to read contactless passes carried by NFC smartphones. In the SmartReader operating mode, the reader is standalone to run and the computer receives RFID/NFC pass data as if someone would type it on the keyboard.
SpringPass by SpringCard is a service for generating NFC passes in order to dematerialize contactless cards or RFID badges by virtualizing them on mobile phones (smartphones). On Apple iOS (iPhone) architectures, the system is based on Apple VAS technology. On Android architectures, the system is based on Google Smart Tap technology.
SpringCard contactless PC/SC couplers (NFC/RFID HF) can be used to read contactless passes carried by NFC smartphones.
In particular, the Prox’N’Roll HSP PC/SC and the PUCK configured as PC/SC have been certified :
SpringCard PC/SC Couplers like the H663 family (CrazyWriter HSP, Prox’N’Roll HSP, TwistyWriter HSP…) and the new SpringCore family (PUCK…) are well supported by Linux systems thanks the open-source PCSC-Lite stack and its CCID driver. All these devices are easy to operate on early Raspberry Pi with little to no specificities.
This has changed on Raspberry Pi 4 and Raspian Bullseye and their new power-saving policy: by default, the system now shuts down any USB device that appears as being “unused” — which is namely the case of any PC/SC Coupler until a card is inserted or presented ;-).
For correct operations of any SpringCard PC/SC Coupler with a Raspberry Pi 4 and Raspian Bullseye, the integrator must therefore disable the USB power control, and this article explains how to do so. It may also be useful to anyone trying to troubleshoot disconnection issues affecting any PC/SC device when used together with an embedded Linux system where USB power saving is enabled by default.