Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

Importing my PKCS #12 certificate from Internet Explorer fails

  • 3 réponses
  • 23 ont ce problème
  • 13 vues
  • Dernière réponse par superheavy

superheavy
superheavy
more options

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?

Toutes les réponses (3)

guigs
guigs
more options

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
more options

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

superheavy
superheavy Auteur de la question
more options

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.