The tokenME EVO II (often referred to as the EVO v2) is a cryptographic USB token developed by Bit4id for digital signatures and strong two-factor authentication. Driver Installation Guide
According to official technical specifications, the tokenME EVO II adheres to CCID and PC/SC standards, which allows it to be Plug & Play on most modern operating systems.
Windows (Vista, 7, 8, 10, 11): Usually requires no additional driver installation as it uses native system drivers. For advanced management, you can download the Bit4id PKI Manager from the Bit4id Support Portal.
macOS & Linux: Compatible out-of-the-box due to CCID compliance.
Browser Extensions: For using the token in web browsers for digital signatures, you may need to install specific middleware or extensions like those found on Dokobit. Key Features & Specs tokenme evo v2 drivers
Security: Complies with European eIDAS regulations for qualified digital signatures.
Hardware: Secure smart card chip with CC EAL 5+ certification. Standards: Supports PKCS#11 and PKCS#15 APIs. Algorithms: RSA up to 4096 bits and AES 128/192/256-bits. Troubleshooting & Support
PIN Management: If your PIN is locked, you must use the Bit4id PKI Manager software to perform an unlock procedure.
Official Downloads: Always source middleware and drivers directly from the Bit4id Official Site to ensure security. Token me EVO - Bit4id The tokenME EVO II (often referred to as
Linux does not require proprietary kernel modules, but it does require libccid and permissions.
sudo apt update && sudo apt install pcscd libccid
wget https://raw.githubusercontent.com/TokenME/evo-v2/master/92-tokenme-evo-v2.rules
sudo cp 92-tokenme-evo-v2.rules /etc/udev/rules.d/
sudo udevadm control --reload-rules
sudo systemctl restart pcscd
pcsc_scan
TokenME EVO V2 (CCID) 00 00.Note: On Raspberry Pi, ensure you have enough USB power. Use a powered hub if the reader resets during card reading.
# Install PC/SC tools and CCID driver
brew install pcsc-lite ccid
Why Upgrade from V1?
If you’re still on the original TokenME drivers, you’re missing out on:
- 60% faster RSA-2048 key generation on the same hardware.
- Multi-session handling (use two TokenME tokens simultaneously without cross-talk).
- Secure channel updates – firmware updates over a signed, encrypted channel.
4. Bluetooth (Optional add-on)
- Appearance: Integrated or dongle-based.
- Driver type: Virtual COM port driver via Bluetooth stack.
Most driver-related searches focus on the USB-CCID variant, as that is the most common for PC integration. We will focus primarily on that. For Linux (Ubuntu/Debian/Raspberry Pi OS) Linux does not
Security Considerations: Signed vs. Test Drivers
Unverified drivers are a common vector for rootkits. Always check the digital signature of your TokenME Evo V2 drivers:
- Right-click the
.sys file > Properties > Digital Signatures. The issuer should be “TokenME GmbH” with a certificate from DigiCert or GlobalSign.
- If you ever see “Test certificate” or no signature, the driver is for development only. Do not use it on a production machine.
Comparing Driver Performance: Evo V2 vs. Evo V1 and Competitors
| Feature | TokenME Evo V1 Drivers | TokenME Evo V2 Drivers | Competitor X Drivers |
| :--- | :--- | :--- | :--- |
| Max USB Throughput | 12 Mbps (USB 2.0 full) | 480 Mbps (USB 2.0 high) | 12 Mbps |
| Packet Loss at 1M CAN bus | ~0.5% | 0.0% (zero-copy DMA) | ~0.3% |
| OS Support | Win7, Linux 4.x | Win10/11, Linux 5.15+, macOS (Intel) | Win10 only |
| Driver signing | SHA-1 (deprecated) | SHA-256 with EV cert | None |
The TokenME Evo V2 drivers stand out due to their zero-copy DMA implementation on supported USB 3.0 hosts, a feature that dramatically reduces CPU load during high-frequency logging sessions.
Frequently Asked Questions (FAQ)
Using Windows:
# List smart card readers (PowerShell)
Get-WmiObject -Class Win32_PnPEntity | Where-Object $_.Name -like "*smart card*"
Or use certutil -scinfo to test smart card CSP.