On Feb 14, 2010, at 4:05 AM, Kevin Reinholz wrote: > On 02/14/10 01:50 AM, Paul Klissner wrote: >> Kevin, >> >> Sun has an implementation that is built for Solaris 10, >> which you should be able to find at sun.com by searching for PC/SC-lite. >> > Paul, > > I went ahead and downloaded the packages, but before I install them, have you > heard of anyone successfully using these packages in conjunction with Red > Hat's coolkey (apparently not updated since around 2007) and Mozilla Firefox? >
FF on Windows (over an RDP connector), yes. FF on Solaris, I'm pretty sure I recall talking to someone who did, but not 100% positive. Never heard of coolkey. > The reason I ask is because the Sun Studio-compiled pcsc-lite and ccid I > built from the opensource project seem to work fine. Moreover, as of the > latest "betas" from Ludovic Rousseau, both pcsc-lite and ccid build for me > just fine on recent OpenSolaris (snv_132) with gcc. If you have a solution that's working for you that's great. Then you don't necessarily need the Solaris packages, particularly if you're just going to support a single user at a workstation. I remember having trouble getting code to build on x86 awhile back and spent a 30 minutes or so on the phone talking to a Sun engineer who was having trouble getting the open source code to build on x86, so I thought maybe this would give you at least one viable approach if you were spinning on building the Open Source code. > > The problem regardless of how I compile pcsc-lite and ccid is loading the > coolkey pkcs11 module in Firefox. I need to complete that step before I can > access DoD CAC-restricted sites and webmail from OpenSolaris. >> I recently worked with someone who installed the packages on OpenSolaris, >> and I think the only problems they had might have been with USB reader >> support because some of the libusb libraries were moved in OpenSolaris. >> That was easily resolved by creating a logical link or something. >> >> > I think on Solaris 10 the optional libusb packages install in the prefix > /usr/sfw/ whereas in recent Nevada/Indiana builds they install in the system > prefix /usr/ >> If you want to go that route let me know - get the packages and if >> it doesn't work, perhaps we can exchange a couple of e-mails and see if >> I can help you resolve it quickly. I can't invest a lot of time helping >> you make it work on a non-target platform (Solaris 10 is what it >> was designed to conform to for release), but I think it would probably >> work out better for you than what I see below. >> >> > Thank you for your offer to help! > > As I mentioned before, unless I can get coolkey to play nice with the > Sun-provided PC/SC-lite and CCID IFD Handler packages and Firefox, I don't > have much point in running these. The only smart card I use is a DoD CAC, and > coolkey is the only pkcs11 module I know of that will support it. (There are > supposedly newer PIV-compliant smart cards being issued by DoD, but I can say > from experience it's still hit or miss whether a newly issued card will be > one of the old CACs or one of the new PIV-compliant cards). >> It is based on an earlier version of PC/SC-lite from the Open Source gate >> (1.3.2 or something), so it doesn't have dependencies on libHAL, which >> is not in Solaris 10 anyway. It isn't sync'd up with the Open Source code, >> but we do have lots of customers using it, and it actually scales up >> to support hundreds of users running simultaneously doing login to Windows >> in a UNIX/Windows virtual desktop environment. >> >> And it is turnkey. When the packages are installed it is running, >> and enabled/disabled through the Solaris SMF framework. >> > If these Sun-provided packages will work with coolkey and Firefox, this > sounds like the most convenient option. Thanks again for pointing these out > and perhaps I'll give this a try. I'd just try them since they'll overwrite what they need to, and restore the previous system state on package removal. Note: The first time you install you may notice it complaining about some conflicting packages in Solaris, due to vestigial code (from old Smart Card projects that were discontinued awhile ago). Some of which we finally got authority to EOL/remove and may have been pulled from the osol gate, so I'm not sure which conflicts you'll see). In any case the package install errors are a short list which you can just pkgrm. From then on SUNWpcsc installs gracefully. The primary environment we support are the Oracle/Sun Ray networked thin client environment, which scales up to hundreds of users with Sun Ray desktop units (DTUs) and that requires two packages SUNWpcsc (base components) + SUNWpcscdtu (sunray drivers/plugins/conf). Paul _______________________________________________ Muscle mailing list Muscle@lists.musclecard.com http://lists.drizzle.com/mailman/listinfo/muscle
