Created attachment 557133 [details] p12 file & ca keys.rar User Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.0; Trident/5.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET4.0C; .NET CLR 3.0.30729) Steps to reproduce: Hello, I have tried to import p12 and failed for unknown reasons. My operating system is Windows VISTA SP2 32 bits. My attached is the p12 file that I try to import. Note: I attached the public keys of CA too. The password is '1234'. Is a coding problem? In principle, it's encoded in TeletexString. We must use UTF8 coding for the certificates? This error can occur for the fields accents? I need technical assistance, please, because most of p12 files that are generating can't be imported successfully. Thanks and Best Regards, Èric Antonell Technical Department CATCert - Agència Catalana de Certificació Passatge de la Concepció, 11 08008 Barcelona http://www.catcert.cat Actual results: The import failed for unknown reasons. Expected results: The import should import successfully as Internet Explorer, for example.
Severity: normal → critical
Priority: -- → P2
Whiteboard: I can't import PKCS #12 files
Severity: critical → normal
Component: Security → Security: PSM
Priority: P2 → --
Product: Firefox → Core
QA Contact: firefox → psm
I suspect this could be a dupe of bug 564403 which could be a dupe of bug 549418 which could be a dupe of bug 217305.
Whiteboard: I can't import PKCS #12 files
Hello Sr. Hughes, Yes, I red this bugs and I saw that these bugs not yet closed. Do you have a joint resolution? In one of the bugs (217305) I saw you speak FriendlyName field, precisely, our developer has provided a script to shorten the field and it maked with different encoding from Unicode. Have a patch or have found a solution? Thanks and Best Regards, Èric Antonell Technical Department CATCert - Agència Catalana de Certificació Passatge de la Concepció, 11 08008 Barcelona http://www.catcert.cat
We don't have a joint resolution. However, we can resolve this bug as a duplicate of bug 217305 and you can follow along in that bug. Is bug 217305 a duplicate of this bug?
Yes, more or less it's the same incidence but the bug 217305 talks about linux platform and in my case is Windows. However, my case is when I import, I think the bug that we have commented is when the user wants to export. To provide more data, the encoding field is BMPString and the version I use is Firefox 6.1. Due to accents and characters of our language, the Telexstring or BMPString encoding is the most recommended. In that moment, the conclusion is a NSS problem or is a different issue? What do you think? Additionally, I tried to export the P12 with Internet Explorer and later try to import in Firefox but the result is just as bad. Although, in Explorer I can import this p12. Thank you, Èric Antonell Technical Department CATCert - Agència Catalana de Certificació Passatge de la Concepció, 11 08008 Barcelona http://www.catcert.cat
Created attachment 563356 [details] Examples of good and bad profile to import in Firefox Mr Hughes, I inform you that I have found a particular certificate profile that works successfully when it imported with Firefox. I have read the rest of bugzilla’s (with the same problem) and you recommend that the Friendly Name must be in UTF8. Interestingly, the profile that I have commented the Friendly Name it's in TeletexString. I attach the profile that works (good-profile) and what doesn’t work (bad-profile). The coding is the same, only varying lengths of some fields in the DN. These are preproduction and the password for import is 1234. My question is: What field of the certificate you read when importing in Firefox? This answer is very important to find a problem. Thank you and best regards, Èric Antonell CATCert – Agència Catalana de Certificació www.catcert.net
I'm not 100% sure if it's a duplicate or not as I am not an expert NSS developer. I'll defer to the development team to make that call.
This will work when we use the sqldb.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 months ago
Priority: -- → P3
Resolution: --- → DUPLICATE
Duplicate of bug: 783994
You need to log in before you can comment on or make changes to this bug.