I don't understand the answer. That implies that no third party application can make use of the certificates/keys contained within the Netscape/Mozilla standard databases. Does that imply the only way for third party applications to make use of these user certificates is to export them to a PKCS12 file and import them into the Microsoft certificate store?
Take for example a user that has a certificate(s) contained within the Netscape browser for use with browser related stuff, and he also has a desire to use those same certificate(s) for SSH-2 public/private key authentication, or for a Windows based SSL/TLS telnet/ftp client. If the certificate was contained within the Microsoft browser, all the Windows based application would have to do is obtain the public key from the certificate using the Microsoft crypto API.. Then when the Windows client needed to authenticate a challenge using the private key operations, it would simply make a request to the API to do a private key signing operation. This is the same exact authentication method being performed by the broswer itself. And by not testing on the most wide spread Windows based OS, you are almost telling us developers to use the Microsoft browser and Microsoft crypto API only! To add insult to injury, you also state that not only do you not test, you don't even use the dll's on any system! Ken "Wan-Teh Chang" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Kenneth R. Robinette wrote: > > > Has anyone used NSS-3.3 on Windows, compiled into dll's and used by several > > different clients concurrently? > > > This should work if the different clients don't share > the NSS config directory or database files. > > > Also, has anyone tried the latest code on Windows 98? > > > We (the NSS team) haven't. We only do QA on Windows NT > 4.0 and 2000. > > The latest NSS code has been run as part of the Mozilla > client on Windows 98, although Mozilla is linked with > our static libraries, not DLLs. This will change soon. > > Wan-Teh >
