For what it's worth, if you /must/ use Chrome..

I've heard support folks talk about how Chrome had it's own SSL
implementation,
and that caused problems with some smart card middlewares.

One solution would be to start chrome with the --use-system-ssl
command-line argument,
to make it fall "back" to the native SSL instead of it's own.

I've also found this one:

http://code.google.com/p/eid-mw/wiki/ChromeLinux

Although it's not about cac, it describes how to enable a pkcs11 module
in Chrome.. might be useful..
substitute 'Coolkey' for 'Belgium eID' and the path of the coolkey
pkcs11 module for '/usr/lib/libbeidpkcs11.so'.

WKR
-f

On 06/25/12 16:47, Michael StJohns wrote:
> I don't use Chrome, but I think it supports PKCS11.  I'd try that approach with the musclecard PKCS11 implementation and the CAC and coolkey plugins.
>
> Mike
>
>
> At 09:08 PM 6/24/2012, Howdy Doody wrote:
>> Hello,
>>
>> I have been unable to find an answer to this anywhere else, but is there
>> any way, at all, to use my cac reader in Linux with google chrome, or am
>> I doomed to have to continue using firefox with cackey or coolkey?
>>
>>
>> _______________________________________________
>> Muscle mailing list
>> Muscle@list...
>> http://lists.drizzle.com/mailman/listinfo/muscle
>
> _______________________________________________
> Muscle mailing list
> Muscle@list...
> http://lists.drizzle.com/mailman/listinfo/muscle
>