Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Caută ajutor

Atenție la excrocheriile de asistență. Noi nu îți vom cere niciodată să suni sau să trimiți vreun SMS la vreun număr de telefon sau să dai informații personale. Te rugăm să raportezi activitățile suspecte folosind opțiunea „Raportează un abuz”.

Află mai multe
Firul de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.
Arhivate

Importing my PKCS #12 certificate from Internet Explorer fails

Firefox Confidențialitate și securitate
superheavy a răspuns la acum 12 ani
superheavy
superheavy

Whenever I try to import my client certificate to authenticate myself on certain websites from Internet explorer to Firefox, I receive an error box that has the message:

"The PKCS #12 operation failed for unknown reasons."

What a super helpful message.

I've exported the certificate from Internet explorer including the private key into a PKCS #12 file.

I've had a certificate that was successfully imported into Firefox in the past that I've tried to re-import as a test, and that also failed. What's the deal?

Whenever I try to import my client certificate to authenticate myself on certain websites from Internet explorer to Firefox, I receive an error box that has the message: "The PKCS #12 operation failed for unknown reasons." What a super helpful message. I've exported the certificate from Internet explorer including the private key into a PKCS #12 file. I've had a certificate that was successfully imported into Firefox in the past that I've tried to re-import as a test, and that also failed. What's the deal?

Toate răspunsurile (3)

guigs
guigs

Hi superheavy, In version 31 there was an update to the Certificate Verification in gecko. It is called mozilla::pkix

Mozilla's included CA Certificate List

guigs
guigs

May also be affected by this bug https://bugzilla.mozilla.org/show_bug.cgi?id=1049435

superheavy
superheavy Deținătorul întrebării

Seems to be the same issue. The process outlined in that bug report is the same I follow, even for verification. Guess it's a confirmed bug and I need to wait.