On 2/17/10 9:42 AM, Wan-Teh Chang wrote: > On Sun, Feb 14, 2010 at 6:57 PM, Subrata Mazumdar > <subrata.mazum...@ieee.org> wrote: > >> Hi, >> >> My experience so far is that PSM Certificate Manager is never launched when >> PKCS#12 link is clicked. Not on Windows. Not on Linux (as described by the >> bug filer). Do not remember for Mac OS X. >> >> Here is what I think is the explanation for the behavior on windows: >> >> On Windows PKCS#12 file type is associated with MS Crypto certificate >> manager. So when someone clicks on the PKCS#12 file link, Windows crypto >> manager is launched for importing the keys/certificates. >> >> Since IE and Chrome (do not know about Safari and Opera) uses the same >> Windows Crypto DB/Manager, the imported keys/certificates in PKCS#12 is >> always visible to both browsers. FF does not uses Windows CertDB - FF uses >> it's own CertDB. As a result, imported key/cert is not visible in PSM >> certificate manager. >> > This is correct. > > The user who reported that bug did not realize that Firefox is not > using the Windows system certificate store, so the user had the > wrong expectations. > > In any case, both Nelson and I have posted comments in that > bug report. >
Do you see the logic of the user who had the wrong expectations here? Is there logic in reassessing the current functionality as it is shipped? I have been told that Firefox is the only one of the 5 major desktop browsers that functions in the way that it does (i.e. the other browsers all have handlers for application/x-pkcs12.) -- Gen Kanai
-- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
