{"id":203102,"date":"2018-04-08T09:53:24","date_gmt":"2018-04-08T07:53:24","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=203102"},"modified":"2018-04-08T09:53:24","modified_gmt":"2018-04-08T07:53:24","slug":"site-betreiber-mit-symantec-zertifikaten-mssen-handeln","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2018\/04\/08\/site-betreiber-mit-symantec-zertifikaten-mssen-handeln\/","title":{"rendered":"Site-Betreiber mit Symantec-Zertifikaten müssen handeln"},"content":{"rendered":"

Betreiber von Webseiten, die diese, f\u00fcr die https-<\/em>\u00dcbertragung (TLS) mit Zertifikaten abgesichert haben und immer noch auf Symantec setzen, sollten schnellstm\u00f6glich handeln.<\/p>\n

<\/p>\n

\"\"Ich hatte es bisher nicht im Blog thematisiert: Google hat Symantec wegen fehlerhaft ausgestellter Zertifikate gesperrt. Auf dem Google Webmaster-Blog findet sich dieser Beitrag<\/a> vom 4. April 2018, in dem Google nochmals auf den Sachverhalt hinweist. In diesem Beitrag<\/a> hatte Google im September 2017 darauf hingewiesen, dass das Vertrauen in Symantec-Zertifikate binnen 13 Monaten entzogen werde. Das Ganze erfolgt stufenweise \u2013 die folgende Tabelle nennt Daten.<\/p>\n\n\n\n<\/colgroup>\n\n\n\n\n\n\n\n\n\n
\n
Date<\/span><\/div>\n<\/td>\n
\n
Event<\/span><\/div>\n<\/td>\n<\/tr>\n
\n
Now<\/span><\/div>\n
through <\/span><\/div>\n
~March 15, 2018<\/span><\/div>\n<\/td>\n
\n
Site Operators using Symantec-issued TLS server certificates issued before June 1, 2016 should replace these certificates. These certificates can be replaced by any currently trusted CA.<\/span><\/div>\n<\/td>\n<\/tr>\n
\n
~October 24, 2017<\/span><\/div>\n<\/td>\n
\n
Chrome 62 released to Stable, which will add alerting in DevTools when evaluating certificates that will be affected by the Chrome 66 distrust.<\/span><\/div>\n<\/td>\n<\/tr>\n
\n
December 1, 2017<\/span><\/div>\n<\/td>\n
\n
According to Symantec, DigiCert's new \"Managed Partner Infrastructure\" will at this point be capable of full issuance. Any certificates issued by Symantec's old infrastructure after this point will cease working in a future Chrome update.<\/span><\/div>\n
 <\/div>\n
From this date forward, Site Operators can obtain TLS server certificates from the new Managed Partner Infrastructure that will continue to be trusted after Chrome 70 (~October 23, 2018). <\/span><\/div>\n
 <\/div>\n
December 1, 2017 does not mandate any certificate changes, but represents an opportunity for site operators to obtain TLS server certificates that will not be affected by Chrome 70's distrust of the old infrastructure.<\/span><\/div>\n<\/td>\n<\/tr>\n
\n
~March 15, 2018<\/span><\/div>\n<\/td>\n
\n
Chrome 66 released to beta, which will remove trust in Symantec-issued certificates with a not-before date prior to June 1, 2016. As of this date Site Operators must be using either a Symantec-issued TLS server certificate issued on or after June 1, 2016 or a currently valid certificate issued from any other trusted CA as of Chrome 66.<\/span><\/div>\n
 <\/div>\n
Site Operators that obtained a certificate from Symantec's old infrastructure after June 1, 2016 are unaffected by Chrome 66 but will need to obtain a new certificate by the Chrome 70 dates described below.<\/span><\/div>\n<\/td>\n<\/tr>\n
\n
~April 17, 2018<\/span><\/div>\n<\/td>\n
\n
Chrome 66 released to Stable.<\/span><\/div>\n<\/td>\n<\/tr>\n
\n
~September 13, 2018<\/span><\/div>\n<\/td>\n
\n
Chrome 70 released to Beta, which will remove trust in the old Symantec-rooted Infrastructure. This will not affect any certificate chaining to the new Managed Partner Infrastructure, which Symantec has said will be operational by December 1, 2017.<\/span><\/div>\n
 <\/div>\n
Only TLS server certificates issued by Symantec's old infrastructure will be affected by this distrust regardless of issuance date.<\/span><\/div>\n<\/td>\n<\/tr>\n
\n
~October 23, 2018<\/span><\/div>\n<\/td>\n
\n
Chrome 70 released to Stable.<\/span><\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Am 17. April 2018 wird der Google Chrome Browser Version 66 freigegeben. Webseiten die ein vor dem 1. Juni 2016 ausgestelltes SSL\/TLS-Zertifikat von Symantec verwenden, werden im Chrome 66 nicht mehr angezeigt. <\/p>\n

\"SSL\/TLS-Zertifikatswarnung<\/p>\n

Der Google Chrome gibt dann eine SSL\/TLS-Zertifikatswarnung mit dem Hinweis auf die Zertifikatssperre aus. Ab dem Google Chrome 70 (erste Builds ab Juli 2018, Final ab Oktober 2018) werden dann \u00fcberhaupt keine Zertifikate mehr von Symantec akzeptiert. <\/p>\n

Die Symantec-Zertifizierungsstelle hat Zertifikate f\u00fcr eine Reihe von Marken wie Thawte, VeriSign, Equifax, GeoTrust und RapidSSL ausgegeben. Symantec hat hier eine (Englische) Webseite zum Thema freigeschaltet. Symantec hat die Zertifikatsausstellung beendet und dieses Gesch\u00e4ft an Digicert verkauft<\/a>. Das TLS-Zertifikat einer Website l\u00e4sst sich \u00fcbrigens auf Seiten wie ssl-trust.com<\/a> im Browser pr\u00fcfen.<\/p>\n

\u00c4hnliche Artikel:
<\/strong>Zertifikatfehler bei Google Chrome\/Slimjet-Browser fixen<\/a>
Microsoft live.com\/Hotmail-Login-Probleme im Firefox (OCSP-Zertifikat)<\/a>
SSL-Zertifikate-Verwirrung bei Let's Encrypt und Symantec<\/a>
Slimjet-Browser: Weitere Updates fixen Zertifikateprobleme<\/a>
Chrome-Bug zeigt https als unsicher an<\/a>
Google unsicher? SHA-1-Kollateralsch\u00e4den im Google Chrome<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Betreiber von Webseiten, die diese, f\u00fcr die https-\u00dcbertragung (TLS) mit Zertifikaten abgesichert haben und immer noch auf Symantec setzen, sollten schnellstm\u00f6glich handeln.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1356,426],"tags":[984,4328,1468],"class_list":["post-203102","post","type-post","status-publish","format-standard","hentry","category-google-chrome-internet","category-sicherheit","tag-google-chrome","tag-sicherheit","tag-zertifikate"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/203102","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/comments?post=203102"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/203102\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=203102"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=203102"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=203102"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}