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 >
-- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
