Ce site disposera de fonctionnalités limitées pendant que nous effectuons des opérations de maintenance en vue de vous proposer un meilleur service. Si un article ne règle pas votre problème et que vous souhaitez poser une question, notre communauté d’assistance est prête à vous répondre via @FirefoxSupport sur Twitter, et /r/firefox sur Reddit.

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

certdata.txt is including 2 expired certificates

  • 2 réponses
  • 1 a ce problème
  • 28 vues
  • Dernière réponse par vlours

more options

Dear Firefox support,

I would like to share with you that your certdata.txt file is including 2 expired CA certificates: | Expiration date | Certificate CN | | 2019-07-06 | Class 2 Primary CA | | 2019-07-09 | Deutsche Telekom Root CA 2 |

New certificates should be retrieved for these 2 CA, or they should be deleted from the certdata.txt as they are no longer valid.

certdata.txt References:

 nss: 'https://hg.mozilla.org/projects/nss/raw-file/default/lib/ckfw/builtins/certdata.txt',
 central: https://hg.mozilla.org/mozilla-central/raw-file/default/security/nss/lib/ckfw/builtins/certdata.txt',
 beta: https://hg.mozilla.org/releases/mozilla-beta/raw-file/default/security/nss/lib/ckfw/builtins/certdata.txt',
 release: 'https://hg.mozilla.org/releases/mozilla-release/raw-file/default/security/nss/lib/ckfw/builtins/certdata.txt',

Thanks for your help.

Dear Firefox support, I would like to share with you that your certdata.txt file is including 2 expired CA certificates: | Expiration date | Certificate CN | | 2019-07-06 | Class 2 Primary CA | | 2019-07-09 | Deutsche Telekom Root CA 2 | New certificates should be retrieved for these 2 CA, or they should be deleted from the certdata.txt as they are no longer valid. certdata.txt References: nss: 'https://hg.mozilla.org/projects/nss/raw-file/default/lib/ckfw/builtins/certdata.txt', central: https://hg.mozilla.org/mozilla-central/raw-file/default/security/nss/lib/ckfw/builtins/certdata.txt', beta: https://hg.mozilla.org/releases/mozilla-beta/raw-file/default/security/nss/lib/ckfw/builtins/certdata.txt', release: 'https://hg.mozilla.org/releases/mozilla-release/raw-file/default/security/nss/lib/ckfw/builtins/certdata.txt', Thanks for your help.

Solution choisie

Hi vlours, you are very observant! However, it's outside the scope of the support forum.

Maybe a good place to discuss this would be the security policy mailing list:

https://lists.mozilla.org/listinfo/dev-security-policy

I wonder whether it is necessary to keep these in the file because there are intermediate certificates they were used to sign. Or would those intermediate certificates also be invalid now? I have no idea...

Lire cette réponse dans son contexte 👍 0

Toutes les réponses (2)

more options

Solution choisie

Hi vlours, you are very observant! However, it's outside the scope of the support forum.

Maybe a good place to discuss this would be the security policy mailing list:

https://lists.mozilla.org/listinfo/dev-security-policy

I wonder whether it is necessary to keep these in the file because there are intermediate certificates they were used to sign. Or would those intermediate certificates also be invalid now? I have no idea...

more options

Hi Jscher2000,

Thanks for your message and suggestion. I've just posted a message in the "mozilla.dev.security.policy" Group. I hope to hear from them soon.

I will close this question as resolved, as the support forum is not in charge of this kind of issue and actually redirected me to the right community.

Thanks. Cheers,