We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

Entrust G2 Root is not in Mozilla CA Certificate List

  • 2 件の返信
  • 8 人がこの問題に困っています
  • 1 回表示
  • 最後の返信者: williamburn

more options

We have noticed the Entrust G2 Root Certificates are not located in the Mozilla CA Certificate List. We have contacted Entrust and they confirmed that the certificates have been sent to Google, Microsoft, and Mozilla and there was nothing that they could do to fix the problem.

Are there plans to update the listing with the new SHA2 root certificates? We are having trouble with vulnerability false-positives and trust issues due to Mozilla not having these certificates in their store.

https://www.mozilla.org/en-US/about/governance/policies/security-group/certs/included/

We have noticed the Entrust G2 Root Certificates are not located in the Mozilla CA Certificate List. We have contacted Entrust and they confirmed that the certificates have been sent to Google, Microsoft, and Mozilla and there was nothing that they could do to fix the problem. Are there plans to update the listing with the new SHA2 root certificates? We are having trouble with vulnerability false-positives and trust issues due to Mozilla not having these certificates in their store. https://www.mozilla.org/en-US/about/governance/policies/security-group/certs/included/

この投稿は williamburn により に変更されました

選ばれた解決策

hello, the root CA will have to work with mozilla to get these certificates into the trust store of the browser. this issue seems to be tracked in bug# 849950.

この回答をすべて読む 👍 0

すべての返信 (2)

more options

選ばれた解決策

hello, the root CA will have to work with mozilla to get these certificates into the trust store of the browser. this issue seems to be tracked in bug# 849950.

more options

Thanks for the quick reply philip. by the way, i think i accidentally clicked the 'not helpful' -- I misread the button.