A
A
Alexey2017-06-17 09:47:50
Google Chrome
Alexey, 2017-06-17 09:47:50

StartCom certificates don't like google again?

Interested in problems with a particular site to begin with.
182503dc19ef4f9fbd374b3e3656bfcb.png
There may be problems with the issuer of the certificate:
989032cd036a40e8a0ce07624787bd5a.png
The site does not open in Cromium\Chrome Canary versions 61.0.3132 or 61.0.3133.
In Chrome version 59.0.3071.104, 60.0.3107.4, 61.0.3126.0 and in Firefox 54, 55 and IE 11/Edge the site opens.

Answer the question

In order to leave comments, you need to log in

1 answer(s)
S
sim3x, 2017-06-17
@pha

If you don't suffer from conspiracy theories
https://security.googleblog.com/2016/10/distrustin...
Background
On August 17, 2016, Google was notified by GitHub's security team that WoSign had issued a certificate for one of GitHub's domains without their authorization . This prompted an investigation, conducted in public as a collaboration with Mozilla and the security community, which found a number of other cases of WoSign misissuance.
The investigation concluded that WoSign knowingly and intentionally misissued certificates in order to circumvent browser restrictions and CA requirements. Further, it determined that StartCom, another CA, had been purchased by WoSign, and had replaced infrastructure, staff, policies, and issuance systems with WoSign's. When presented with this evidence, WoSign and StartCom management actively attempted to mislead the browser community about the acquisition and the relationship of these two companies. For both CAs, we have concluded there is a pattern of issues and incidents that indicate an approach to security that is not in concordance with the responsibilities of a publicly trusted CA.
https://groups.google.com/forum/#!topic/mozilla.de...

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question