Help Retrieving VeraCrypt Keys from a Athena Smartcard Solutions Card

[KM6]

Hi,

A short time ago my pc (Win10x64) blew and I need to get the Veracrypt keys on the new computer (Win10x64). The keys are stored on a Athena Smartcard Solutions Card, which is read by the Athena AseIIIe Smartcard Reader which plugs into usb. The problem is that Veracrypt communicates with the card via a PKCS#11 library, which I do not have. Unfortunately, it seems impossible to get hold of the official Athena middleware which would install the PKCS#11 library (asepkcs.dll for Athena), since Athena does not exist anymore.

I did find this: 32-bit asepkcs.dll v6.5.0.5 from https://www.pconlife.com/download/ot...cd61010030f4e/
The asepkcs.dll looks legit, at least it is signed by Athena Smartcard Solutions (but I am still apprehensive about using it).


The massive problem at the minute, is that if the smartcard got damaged in some way, I can never recover the keys, and would lose 20+ years' worth of data! Therefore, I would much appreciate any advice on how to proceed.

[jmarket]

Hi there KM6 ,

That’s a tough situation — and you’re absolutely right to be cautious. Since Athena Smartcard Solutions no longer exists, obtaining legitimate middleware can be difficult, but installing any DLL from third-party or “DLL download” sites is not recommended. These sources are commonly abused to distribute tampered or malicious files, even when they appear to be signed.

---

✅ Recommended Next Steps

1. **Do not install or register asepkcs.dll from unverified sources.**
Even a genuine digital signature can be spoofed or from an outdated certificate chain. Running it could compromise the integrity of your new system or your encrypted data.

2. **Check if another vendor now maintains Athena’s middleware.**
- Athena’s smartcard business was eventually absorbed into NXP Semiconductors and later Thales Group (Gemalto SafeNet line).
- You may find compatible middleware through Thales’ “SafeNet Authentication Client” or NXP’s legacy driver archives.
- Look specifically for “ASEDrive IIIe PKCS#11 module” or “asepkcs.dll” under official OEM rebranding.

3. **Use the Wayback Machine (archive.org)**
Search for archived downloads from athena-scs.com or athena-scs.com/support.
Sometimes the original ASE middleware installers (with asepkcs.dll included) are still retrievable from snapshots dated between 2013–2017.

4. **Try alternative middleware options**
If you can identify the smartcard’s chip model, you may be able to use a compatible generic PKCS#11 provider (such as OpenSC) configured to point to your reader’s driver.
- OpenSC (official site)
- Once installed, test detection with:

pkcs11-tool --list-slots

5. **Backup the smartcard data immediately if possible.**
If the card is still readable, use Veracrypt’s built-in keyfile export or duplication tools to generate a secondary recovery token. This ensures you have redundancy in case the card fails physically.

6. **Contact Veracrypt support directly.**
They may have handled similar legacy middleware issues and can provide guidance on importing keys using another PKCS#11 provider.

---

⚠️ Important Note

Do not attempt to brute-force or manually extract keys from the card. Smartcards include tamper protection that can permanently lock or wipe data if accessed improperly.

If your card becomes unreadable, professional data recovery through a smartcard forensic service may be your only remaining option.

---

💬 Summary

Stick to official or archived Athena/Thales/NXP sources, avoid unverified DLLs, and create a redundant backup of your keys as soon as the card is accessible.
With careful handling and the right PKCS#11 module, you should be able to regain access safely.

[KM6]

jmarket
Thank you for the concern, and even more thanks for the great suggestions.
So far, I've written to Thales Group Support asking for direct help since I didn't find anything yet on their site.
I will now try the Wayback machine- I would've NEVER thought of that!
Thanks again, this has been tremendously helpful.

[jmarket]

That’s great to hear — I’m really glad the suggestions helped!
Reaching out to Thales directly was an excellent move; if anyone can provide legitimate middleware or a verified replacement, it’ll be them. The Wayback Machine is also surprisingly effective for recovering legacy drivers and documentation, so you’re definitely on the right track.

If you do manage to locate an authentic Athena or Thales installer, feel free to share the version details here — it could help others in the same situation down the road.

Best of luck getting those keys accessible again, and don’t hesitate to check back in if you hit another wall — we’re happy to help however we can. 👍