Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

Entrust G2 Root is not in Mozilla CA Certificate List

  • 2 risposte
  • 8 hanno questo problema
  • 174 visualizzazioni
  • Ultima risposta di 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/

Modificato da williamburn il

Soluzione scelta

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.

Leggere questa risposta nel contesto 👍 0

Tutte le risposte (2)

more options

Soluzione scelta

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.