Re-read my initial post, and I asked the wrong question. It was written in haste, my apologies. Let me clarify...
We're actually not looking to replace the SSL engine in Firefox, but just use a different crypto provider (I was thinking OpenSSL crypto "engine" when I wrote the message). We're developing a hardware device similar to a crypto accelerator and, when it is installed on the local machine, we would like all SSL-related crypto routines in Firefox to be redirected to our device. My hardware developers tell me this could be quite cumbersome if we're not implementing the full PKCS#11 interface. I'm just looking to find out whether it can be done without implementing all the authentication features of PKCS#11. Thanks, Dan LDE Global Innovations, Inc. "Nelson B" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Dan M wrote: >> Hello, >> >> We've developed a custom SSL provider engine and would like to be able to >> use it as the default Firefox engine. We don't want to use it for other >> cryptographic operations because it doesn't fully implement the non-SSL >> related features of PKCS#11. Can this be done easily? >> >> Thanks, >> Dan > > No, it can't be done easily. > > Why would it be a good idea for users to be able to replace such a > crucial security component easily? > > -- > Nelson B _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
