At least two users have reported on SUMO [1] [2] that they can't import the Spanish government's DNIe certificates [3] into Win64 Firefox's Certificate Manager. They had successfully imported the same certificates into 32-bit Firefox in the past. I have not reproduced the problem, but here are the reported steps to reproduce: 1. Load about:preferences#privacy 2. Click the "View Certificates" button to open Firefox's Certificate Manager. 3. Click the Certificate Manager's "Import" button to open a file dialog. 4. Select the DNIe certificate file with .p12 or .pfx filename extension. 5. Enter the certificate password, if necessary. Result: The user reports that nothing happens. The certificate is not imported and there are no error messages that indicate a file. [1] https://support.mozilla.org/es/questions/1178928 [2] https://support.mozilla.org/es/questions/1178673 [3] https://www.dnielectronico.es/

Do you have a copy of the file they're trying to import?

(In reply to David Keeler [:keeler] (use needinfo?) from comment #1) > Do you have a copy of the file they're trying to import? Unfortunately, no. If these certificates are personal identification, users might not want to share them with us, but I will ask.

Rubén, do you have DNIe certificate? Can you reproduce this bug with Win64 Firefox?

I don't, but let me ping other people.

A user reported on SUMO that they can reproduce this DNIe problem in both 32-bit Firefox 56.0 and 64-bit Firefox 56.0.1, but it used to work in earlier Firefox versions. So this appears to be a regression in Firefox 56.0 and not specifically a 64-bit bug. https://support.mozilla.org/en-US/questions/1178673#answer-1015451

We could successfully import Spanish certificates in Firefox 56.0 Win64, with the following steps: - Export FNMT certificate to .p12 - In Firefox 54.0, import it successfully - Upgrade to Firefox 56.0 - Certificate still here - Remove it, reimport it sucessfully - Import another .p12 file successfully Note: we did this on a blank profile. Maybe we could suggest to reimport their certificates in a blank profile, and see if their profile got like "corrupted" during upgrade?

Mathieu, can you reproduce this in 57/58? Are your steps in comment 6 a workaround, or steps to reproduce, or both? Chris, since I'm not seeing a lot of duplicate reports of this I'm not thinking of it as a 56 dot release driver. Are the users you're in contact with able to work around the issue with a new profile?

(In reply to Liz Henry (:lizzard) (needinfo? me) from comment #7) > Chris, since I'm not seeing a lot of duplicate reports of this I'm not > thinking of it as a 56 dot release driver. Are the users you're in contact > with able to work around the issue with a new profile? I don't think this is a 56 dot release driver. The user said pre-56.0 builds worked correctly, but they haven't replied to suggestions to test a new profile: https://support.mozilla.org/en-US/questions/1178673#answer-1015451

Looks like the french lawyer bar has a similar issue: https://twitter.com/e_barreau/status/920683881141071872 (I reached out to them)

> Mathieu, can you reproduce this in 57/58? We haven't tried. If the coworker that had a Win64 install comes around, we'll try! > Are your steps in comment 6 a workaround, or steps to reproduce, or both? I don't think it's a workaround, we more or less tried to reproduce what was described on SUMO reports.

The SUMO reporter says that they was able to successfully import and export their certificates in 64-bit Firefox 56.0 after "refreshing" their user profile in about:support. https://support.mozilla.org/en-US/questions/1178928#answer-1019000 @ Sylvestre: any updates from the e_barreau Twitter thread in comment 9? I think we should understand that issue before resolving this bug as WORKSFORME.

They told me that it is likely not related.