clone 380275 -1 -2 rename -1 Belgian_eID_PKCS11_java.cfg contains wrong path severity -1 important rename -2 The mozilla plugin should be automatically registered upon installation tags -2 + help tags 380275 + confirmed thanks
On Fri, Jul 28, 2006 at 11:01:15PM +0200, Luc Stroobant wrote: > Package: libbeidlibopensc2 > Version: 2.5.9-3 > Severity: normal > > *** Please type your report below this line *** (you're supposed to remove that line ;-) > The install using the included html file: > usr/share/beid/beid-pkcs11-register.html > fails with an error "Unable to add module". I know; this is because the .html file links to the .so file without version number, which is not in that particular package (only in the -dev package). I intend to fix this in a future release, but I first need to ensure that I understand where everything links to and from. Mean time, if you make sure you install all packages from the belpic source package, the .html register script will work. > This package contains a file: > /usr/lib/pkcs11/Belgian_eID_PKCS11_java.cfg > which might also be used to install the module, but using this file also > fails to add the module. > > The contents of the file is: > name = BelgianEID > library = /usr/local/lib/libbeidpkcs11.so > > That path is wrong, the right path to the library is: > /usr/lib/libbeidpkcs11.so That's a different bug, actually. Thanks for pointing me to it, hadn't found out about that one ;-) > When you open the above lib in the "load security device" options of > Firefox. The security device can be added correctly. > > Since the documentation at http://eid.belgium.be/ suggests the use of > the HTML file, it might be good to include a README that explains this > other way. Or just to make sure that installing through the HTML file will work, in all circumstances ;-) > It would be even better if the user is prompted at install time with a > question to automatically install the Firefox security device. After > all, this is probably the part of the software most users like to use... I agree, but it's unclear to me whether this is possible, and if so, how I would go about doing it. In any case, you would still need to manually confirm the validity of the certificates (and I will *not* do this automatically, not even if it were possible), so I'm not entirely sure it would help that much. Anyway, two bugs have been split off, and some have received tags. The rest is for some other day ;-) -- Fun will now commence -- Seven Of Nine, "Ashes to Ashes", stardate 53679.4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
