(old)Puppy Linux Discussion Forum

DoD CAC Card how-to.

### Update ###
I added a CACKey-0.6.8.pet on the Forge site so no need to build from source.

Updated instructions.


This is how I got the SCR3310v2 CAC card reader to work in Precise Puppy 5.5 with DoD CAC v 0.6.8.

Download and install the following packages:
1. pcsc-tools_1.4.18-1 & all dependencies (Ubuntu-Precise-Universe)
2. pscsd_1.7.4 & all dependencies
(Ubuntu-Precise-Universe)
3. Firefox-19.sfs
(http://www.murga-linux.com/puppy/viewtopic.php?t=84802)
4. Firefox add-on: DoD Configuration 1.3.6
(http://www.forge.mil/Community.html)
5. Go to Forge.mil to download the CACKey-0.6.8.pet (DoD only): (http://www.forge.mil/) search for the CACKey project once logged in.


Instructions:
1. Attach SCR3310v2 CAC reader
Check it, run the following command
# pcsc_scan

This should detect the card SCR3310v2 CAC reader.

2. Next we will install the CACKey packages, notably it will install libcackey_g.so & libcackey.so modules in /usr/local/lib/

3. Now to update and load the certs. Start Firefox (assuming that the Firefox add-on is installed) go to tools>add-ons in the DoD Configuration 1.3.6 add-on select preferences and click "Update DoD certs" and click "Update Federal Certs."

Note! Do NOT click "Redetect Smart Card Reader" this will crash the browser.

4. To make the CAC certs available to the browser do the following.

In Firefox, edit>preferences>advanced>encryption>security devices

Click load, for the modulename call it “CAC

Unfortunately does not detect my IOGEAR GSR202 which is the only CAC Reader that they sell in my area and the most common one used here, I attempted to recompile the drivers from IOGEAR's site but it did no good. I tried something similar to what you have up with a SCR-3310 v2 a while ago which is still the "standard" for CAC readers in the military and only had limited success back then with getting it to work (in Ubuntu but didn't work at all in Puppy).

figured out the problem, apparently the newest libccid doesn't support alcor micro based readers so I had to fall back to an older version (1.3.11) which supports both iogear and the common SCR3310v2

Fantastic, thanks for researching the fix on this!