I thought _System wasn't compatibly? Maybe _stdcall?
I think we are using PR_CALLBACK in these cases which is _Optlink. We tried to
create an NSS_CALLBACK but noone thought it was the right thing.
We can't change PR_CALLBACK to _System because that breaks the world...
Mike
Julien Pierre wrote:
> Michael,
>
> Michael Kaply wrote:
>
> > Is there a bug open on this?
> >
> > This seems bad.
>
> As fas I know, it's a feature of NSS to automatically look for the root cert
> module and store it . The problem here may be that the two compilers
> generate incompatible binaries and you cannot mix them.
>
> secmod.db is a database which contains a list of PKCS#11 cryptographic
> modules. PKCS#11 modules are implemented as shared libraries on Unix or DLLs
> in OS/2 & Windows. Their purpose is to access special cryptographic devices,
> such as smart card readers, or provide other security functionality.
> Obviously the PKCS#11 modules need to be built with the same compiler as the
> application that loads them. That isn't specific to nssckbi.dll, which
> happens to be a PKCS#11 module that ships with NSS and contains a list of CA
> certificates. The only real answer here to solve the problem would be to use
> a common calling convention for PKCS#11 calls that would allow the nssckbi
> from one compiler to load in the browser application built with another, eg.
> _System. This should work because the PKCS#11 interface is procedural C, not
> object oriented.
>
> >
> >
> > Mike Kaply
> > IBM
> >
> > Julien Pierre wrote:
> >
> > > Jens,
> > >
> > > Jens Manfredson wrote:
> > >
> > > > The following I found in the file secmod.db:
> > > >
> > > > Builtin Roots Module
> > > > /F:\INTERNET\CLIENTS\MOZILLA_EMX\BIN\nssckbi.dll
> > > >
> > > > This hard coded path to my EMX version causes the VACPP version to
> > > > crash!!
> > > >
> > > > Jens
> > >
> > > The first time an NSS program loads, it will attempt to load nssckbi -
> > > the root certificate module , and then store its location into the
> > > secmod database. If you migrated your profile from EMX to VACPP, this
> > > would happen. Just delete the secmod.db and everything will be OK - a
> > > new secmod.db will be created automatically with a pointer to correct
> > > version of nssckbi found in your LIBPATH.
>
> --
> The network is the computer, and it's down
