Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

Entrust G2 Root is not in Mozilla CA Certificate List

  • 2 respostas
  • 8 têm este problema
  • 1 exibição
  • Última resposta de 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/

Alterado por williamburn em

Solução escolhida

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.

Ler esta resposta 👍 0

Todas as respostas (2)

more options

Solução escolhida

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.