{"id":8192,"date":"2018-12-13T16:58:27","date_gmt":"2018-12-13T21:58:27","guid":{"rendered":"https:\/\/www.thesslstore.com\/blog\/?p=8192"},"modified":"2018-12-14T07:34:41","modified_gmt":"2018-12-14T12:34:41","slug":"sectigo-to-start-issuing-from-new-roots-on-january-14th","status":"publish","type":"post","link":"https:\/\/www.thesslstore.com\/blog\/sectigo-to-start-issuing-from-new-roots-on-january-14th\/","title":{"rendered":"Sectigo to start issuing from new Roots on January 14th"},"content":{"rendered":"<h2>The Comodo CA roots are out, USERTrust roots will replace them<\/h2>\n<p>Last month we were excited to share news that one of our biggest partners, <a href=\"https:\/\/www.thesslstore.com\/blog\/comodo-ca-changes-its-name-to-sectigo\/\">Sectigo, was changing its name from Comodo CA<\/a>. It was a much-needed move as Comodo Group, the company Sectigo split from, operates in the same space and had, more or less the same colors and logo.<\/p>\n<p>Thus, Sectigo was born.<\/p>\n<p>Now, <a href=\"https:\/\/sectigo.com\/sectigo-story-faq\">in an announcement made today<\/a>, Sectigo is entering the next phase of its transition: it\u2019s swapping out the old Comodo CA roots come January 14, 2019.<\/p>\n<p>So, today we\u2019ll keep it short and we\u2019ll discuss what Sectigo is doing and what it will mean to Sectigo customers moving forward.<\/p>\n<p>Let\u2019s hash it out.<span id=\"newline\"><\/span><\/p>\n<h2><img loading=\"lazy\" decoding=\"async\" class=\"alignright size-medium wp-image-7858\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2018\/10\/sectigo_logo_mark_color-228x300.png\" alt=\"Comodo CA changes its name to Sectigo\" width=\"228\" height=\"300\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2018\/10\/sectigo_logo_mark_color-228x300.png 228w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2018\/10\/sectigo_logo_mark_color-768x1012.png 768w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2018\/10\/sectigo_logo_mark_color-777x1024.png 777w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2018\/10\/sectigo_logo_mark_color.png 1305w\" sizes=\"auto, (max-width: 228px) 100vw, 228px\" \/>Let\u2019s start by talking about Root CAs<\/h2>\n<p>While we\u2019re not going to go <a href=\"https:\/\/www.thesslstore.com\/blog\/root-certificates-intermediate\/\">in-depth about Root CAs and Intermediates<\/a>, it is worth just glossing over really quickly so the rest of this information will make a little more sense.<\/p>\n<p>Every operating system maintains a Root store (sometimes called a trust store) that contains a set of root certificates that literally live on your system. These roots are incredibly valuable, because they can be used to issue trusted digital certificates like SSL\/TLS certificates and signing certificates.<\/p>\n<p>When you visit a website and your browser is presented with the site\u2019s SSL\/TLS certificate, your browser <a href=\"https:\/\/www.thesslstore.com\/blog\/tls-1-3-handshake-tls-1-2\/\">performs a series of checks to authenticate it<\/a>. One of those checks involves tracing the signature on the leaf or end-user SSL\/TLS certificate back to the certificate whose key signed it. If it can follow the certificate chain back to one of the roots in whatever trust store it\u2019s using, it will trust the end-user certificate. If not, you get an error and <a href=\"https:\/\/www.thesslstore.com\/blog\/fix-err-ssl-protocol-error\/\">the connection fails<\/a>.<\/p>\n<p>Now, once again, here\u2019s the thing about Roots: they\u2019re powerful, and valuable to the point of being dangerous. The various root programs (Mozilla\u2019s, Apple\u2019s, Microsoft\u2019s, Google\u2019s) are exceedingly stringent in their requirements before adding new roots. CAs must undergo audits, there are review processes and some of the folks running them are a bit\u2026 difficult.<\/p>\n<p>But that\u2019s for good reason, a Root CA can issue trusted certificates, so if it\u2019s ever compromised it\u2019s going to be a full-fledged disaster. This is an eventuality that everyone wants to guard against. It\u2019s why CAs issue intermediate roots and sign certificates with those \u2013 adding an additional layer of protection \u2013 that way should it ever be necessary to revoke one you\u2019re not losing the actual Root. It\u2019s much easier to spin up an intermediate than a Root, as you&#8217;ll see in a moment.<\/p>\n<p>One last thing, whereas publicly trusted leaf certificates have lifespans not exceeding 27 months, Roots can have lifespans of over 20 years.<\/p>\n<h2>Sectigo is changing its Root CAs and its Intermediates<\/h2>\n<p>Ok, now let\u2019s talk about what\u2019s going on with Sectigo and its decision to change roots on January 14th. As we just discussed, CAs typically don\u2019t issue certificates directly off their roots. Instead they spin up intermediate roots and use those to sign.<\/p>\n<p>Currently, this is what the certificate chain for Sectigo\u2019s SSL\/TLS certificate looks like:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-8193 size-full\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2018\/12\/Sectigo-Certificate-Chain.jpg\" alt=\"Sectigo to start issuing from new Roots on January 14th\" width=\"603\" height=\"645\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2018\/12\/Sectigo-Certificate-Chain.jpg 603w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2018\/12\/Sectigo-Certificate-Chain-280x300.jpg 280w\" sizes=\"auto, (max-width: 603px) 100vw, 603px\" \/><\/p>\n<p>Up top you have the Comodo Root CA. Sectigo.com uses an Extended Validation certificate, so you can also see that the EV intermediate was used to sign the Sectigo leaf EV certificate.<\/p>\n<p>Obviously, Sectigo is trying to get away from the Comodo branding, so having Roots and Intermediates that say \u201cComodo\u201d is not desirable.<\/p>\n<p>Personally, I had wondered how Sectigo was going to handle this transition from a PKI standpoint given the time it takes (and the rigor involved with) getting a root accepted into the various root programs. Not to mention the fact I keep pretty close tabs on what\u2019s happening with the Mozilla root program and hadn\u2019t seen anything to indicate an attempt had even been made.<\/p>\n<p>Well, now we know. And the answer involves going back to the past to help sort out the future. Sectigo will begin using its USERTrust Root CAs as opposed to the Comodo Root CAs it had previously been chaining from. The USERTrust root is not new, the first of its ilk was actually created back in 2000 and expires on May 30, 2020. Newer versions have been generated since 2010 with lifespans pushed out as far as 2038. So the USERTrust Root CAs aren\u2019t new, it\u2019s just they don\u2019t have \u201cComodo\u201d in their name.<\/p>\n<p>Using the USERTrust Root CAs, Sectigo will spin up its own branded intermediates so that its certificate chain will reflect its new branding, instead of being a holdover from a previous iteration of the company.<\/p>\n<p>This move will prove doubly useful for Sectigo, too. Not only will it be able to apply its new branding to its intermediates and remove all semblance of Comodo from its certificate chains, but this also gives Sectigo more time to get its dedicated roots into the various root programs. I would imagine eventually the end goal is to have actual Sectigo Root CA certificates, but that obviously doesn\u2019t happen overnight. So, swap roots, spin up new intermediates and take your time on getting the Root CAs accepted.<\/p>\n<p>Makes sense.<\/p>\n<h2>What does this mean for existing Sectigo customers?<\/h2>\n<p>Much like when the <a href=\"https:\/\/www.thesslstore.com\/blog\/only-certificate-authorities-need-to-worry-about-certificate-transparency\/\">Certificate Transparency requirement went into place<\/a>, this is really something that\u2019s only going to affect the Certificate Authority side of things.<\/p>\n<p>As Sectigo <a href=\"https:\/\/sectigo.com\/sectigo-story-faq\">said in its statement<\/a>:<\/p>\n<blockquote><p>We want to assure all customers and partners that this change will happen seamlessly with no action needed.\u00a0 Your existing certificates, issuing CAs, and roots will remain active and trusted.\u00a0 The new Sectigo intermediates will be used to fulfill new requests, renewal requests, and requests that are pending at the time of this transition.\u00a0 Reissuance requests that are handled directly by Sectigo will be fulfilled using the same issuing CA that issued your original certificate.<\/p><\/blockquote>\n<p>Ok, so let\u2019s just run through a few things specifically:<\/p>\n<ul>\n<li>All Sectigo-issued certificates will continue to be trusted globally<\/li>\n<li>No action is required from customers, no need to re-issue or replace certificates until expiration<\/li>\n<li>All current Comodo CA and Sectigo certificates issued off the old roots will continue to work until expiry<\/li>\n<li>Finally, if you have a branded issuing CA, nothing will change with that<\/li>\n<\/ul>\n<p>These changes are set to take effect on January 14, 2019. We will let you know if anything changes between now and then\u2026<\/p>\n<p><em>As always, leave any comments or questions<\/em><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-7276\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2018\/08\/bigstock-222348568.jpg\" alt=\"Hashed Out by The SSL Store is the voice of record in the SSL\/TLS industry.\" width=\"1559\" height=\"407\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2018\/08\/bigstock-222348568.jpg 1559w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2018\/08\/bigstock-222348568-300x78.jpg 300w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2018\/08\/bigstock-222348568-768x200.jpg 768w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2018\/08\/bigstock-222348568-1024x267.jpg 1024w\" sizes=\"auto, (max-width: 1559px) 100vw, 1559px\" \/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The Comodo CA roots are out, USERTrust roots will replace them Last month we were excited to share news that one of our biggest partners, Sectigo, was changing its name&#8230;<\/p>\n","protected":false},"author":6,"featured_media":8195,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":"","tve_updated_post":"","tve_custom_css":"","tve_user_custom_css":"","tve_globals":{},"tcb2_ready":0,"tcb_editor_enabled":0,"tve_landing_page":"","_tve_header":"","_tve_footer":""},"categories":[17],"tags":[221,9550],"class_list":["post-8192","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-industry-lowdown","tag-root-certificates","tag-sectigo","post-with-tags"],"views":15934,"jetpack_featured_media_url":"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2018\/12\/bigstock-215750020_edited.jpg","_links":{"self":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/posts\/8192","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/comments?post=8192"}],"version-history":[{"count":0,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/posts\/8192\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/media\/8195"}],"wp:attachment":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/media?parent=8192"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/categories?post=8192"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/tags?post=8192"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}