Hello people,
This is Arun ....
I'm using USB eTokens (to carry my digital certificates for authentication) with firefox. For the eToken to work, we need to import the corresponding PKCS#11 module in Options -> Security Devices -> Load. In my case this will be the Aladdin driver's module.
I tried to import the same in portable firefox installed in another USB drive (not in the eToken). It is working fine. I need to insert both the USB drive (with Portable Firefox) and eToken (with digital certificate).
But the problem is that, when I use my USB eToken in another machine, the same is not detected by Firefox. This is because the Windows directory is not the same as in machine in which I imported the same.
It is c:\windows\system32\eTpkcs11.dll
But in the machine in which I use, the DLL is present in
h:\windows\system32\eTpkcs11.dll
So everytime, I use it in any other machine which doesn't have a default C: as it's windows directory, I may need to reload my security module. But whenever the
I don't want the same security module to be loaded twice in portable firefox and also whenever the windows is not the default in the machine I use, I may need to load the same once more.
Is there a way to enable portable firefox to retain the loaded security modules irrespective of the windows directory of installation ?
Or is there any way for portable firefox to automatically enumerate the installed security drivers or modules ?
Thanks in advance,
Arun
It sounds to me more like this is simply that the driver needs to be installed on every PC individually, rather than anything to do with where the windows directory is.
The DLL that you mention is not a standard windows file, but is a device driver for your eToken, which means that it almost certainly need to be installed on each machine that you wish to use the eToken on, by an administrator account.
Once it is properly installed in each place, FFP should pick it up correctly.
Edit:
Rereading the OP, you might be saying that you have installed it everywhere already, but that FFP only remembers the last place it picked it up from. If that is the case, then you will probably have to raise the question of auto-scanning with the main Mozilla dev team, rather than here.
Thanks for your comment ....
It is not a problem as we need not give the whole path of the module. As this is driver specific, we just need to provide the PKCS#11 DLL name alone and firefox automatically enumerates the provider.
Arun