On 10/26/2010 12:06 PM, Marcio wrote: > On 26 out, 14:41, Robert Relyea <rrel...@redhat.com> wrote: > >> On 10/26/2010 08:52 AM, Marcio wrote: >> >> >> >> >>> Hi there, >>> >> >>> Running certutil -U -d 'dir of db on my profile' I can not see the >>> token and slot with my certificate. >>> >> >>> I´m using: >>> >> >>> a) certutil (compiled as WIN954_64 with MSVC9 64) >>> b) SafeSign (aetpkss1.dll) (64 bits) >>> c) Gemplus Smart Cardd Reader >>> d) Windows Vista 64 Ultimate >>> >> >>> but, using certutil (compiled as WIN954 with MSVC9) works fine! >>> >> >>> The samething happens with: >>> >> >>> WINNT6_64 (doesn´t work) and WINNT6 (works fine) >>> >> >>> Some idea ? >>> >> Possibly, >> >> If you are using the same NSS db directory in both cases, then, from >> your description, that directory has a pointer to a 32 bit version of >> aetpkss1.dll in secmod.db. When you run 64 bit NSS you can't load the 32 >> bit dll, so NSS doesn't. >> >> You have a coupe of options. >> 1) try the test in a new directory. Make sure your .dll is really 64 bit. >> 2) use the 64-bit modutil to load the 64 bit version of the .dll. Now >> your profile has both versions. The improper version will be ignored >> when NSS loaded. >> >> I used to use option 2 a lot when I had an NSS database on my NFS home >> directory, but would log into a number of different unix machines. >> >> Today I solve the issue on 32bit/64bit linux by using the library path. >> On linux, 32bit applications know that they load from /usr/lib and 64bit >> applications know that they load from /usr/lib64. If I load >> libatepkss1.so rather than /usr/lib/libatepkss1.so I'll get the correct one. >> >> bob >> >> >> >> >>> Thanks >>> >> >>> Marcio- Ocultar texto das mensagens anteriores - >>> >> - Mostrar texto das mensagens anteriores -- Ocultar texto das mensagens >> anteriores - >> >> - Mostrar texto das mensagens anteriores - >> > > Hi Bob, > first of all, thank you for respond. > > Well. Lets go > > 1) I create a new db with modutil: > modutil -create -dbdir . > > 1.1) and when I try to add the module I get the error: 193 > modutil -add "New module" -libfile "C:\Windows\SysWOW64\aetpkss1.dll" - > dbdir . > > ERROR: failed to add module "New module". Probable cause : "error > 193". > > Analysing the aetpkss1.dll with Dependendy Walker I saw that > aetpkss1.dll is an 32 bit which guide me to using a non 64 bit. Even > the package from SafeSign is 64 bits and seems to work on Windows 64. > So if aetpkss1.dll is 32-bit, then it won't work with 64-bit NSS. There isn't a problem running 32-bit apps on 64 bit windows, so it's possible that the SafeSign tools are actually 32-bit.
If safenet as a 64-bit version, then you can use that. > By the way. Loading the module with Mozilla Firefox, I can load it but > I can not see the details and I can not login into. > Executing: modutil -list -dbdir "db of my profile in mozilla" I can > see: > the module: 2. New module > library name: C:\Windows\SysWOW64\aetpkss1.dll > slots: There are no slots attached to this module > > What tell me that I can not see my smart card inserted and get access > to my certificates and private keys > > With modutil and certutil compiled in 32 bits I can see the module and > list the certificate with certutil but I can not use the jss4.dll > compiled with to get access because I get the error from java: > loadLibrary() is not 64 bits. > This is consistent. Clearly aetpkss1.dll is 32-bits. It won't work with 64-bit apps. > What do you suggest ? > Either use 32-bit tools, or find a 64-bit PKCS #11 module for safenet. The 32-bit dll will not work with our 64-bit apps (which is exactly what you are seeing). > Thanks in advance > > Marcio > >
-- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
