David Weekly wrote: > I've just begun to use client certificates, and if you're using > Firefox and click on a .p12 file (which has MIME type application/x- > pkcs12), Firefox on Windows will happily pass off to the Internet > Explorer client certificate import wizard. This is particularly > confusing, since the IE importer is subtle enough that a naive user > (like myself!) might believe that Firefox had properly imported the > client certificate. > > The right answer is to have Firefox register a handler for this MIME > type and prompt the user to import the client certificate. I found > bugs 77355 and 213359, but neither seemed to directly address this > issue...and 77355 is an old and dusty bug that nobody seems to be > paying attention to.
That's because it was filed against the wrong component. I have just changed that. It should get a little closer to the goal now. > Thoughts? Is this lame? Should I file an RFE bug? See also Bug 349112 – TB/SM doesn't import .p12 files sent/received as email It is probably a duplicate of 77355. One of those bugs (77355 or 349112) should be the right one. No point in filing a duplicate. You can add your vote to those bugs. Bug 213359 is specifically about pk12util, a command line tool that uses the same NSS libraries as used by the browser. Getting that bug fixed won't have any effect on the browser. _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
