Last active
May 25, 2016 13:55
-
-
Save robstradling/dc66fd52f686d08a914bc88b2788856b to your computer and use it in GitHub Desktop.
Symantec email to their Partners regarding CT
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
From: Symantec Alert Notification [mailto:[email protected]] | |
Sent: 21 May 2016 | |
Subject: Urgent! Your Immediate Response Is Required | |
Dear Partner, | |
Your immediate response is required to avoid triggering "Untrusted" | |
warnings from Chrome for your customers' websites. | |
We would like to inform you about a new requirement in Google Chrome | |
and how you can help your customers avoid getting "Untrusted" warnings | |
on your customers' websites. | |
What is happening? | |
Google is mandating that on June 1, 2016 all SSL/TLS certificates must | |
be published on the Certificate Transparency (CT) public logs in order | |
for a website to avoid an "Untrusted" warning on Google Chrome. | |
Symantec has identified that you have customers with one or more of | |
Symantec(*) SSL/TLS certificates that have not been published in | |
Certificate Transparency public (CT) logs. Unpublished certificates | |
can be the result of your customers' prior selection to not enable CT | |
during certificate enrollment, or purchase of certificate before CT | |
was available. | |
What do I need to do? | |
In order to prevent these warnings from appearing in Google Chrome, | |
certificates without Certificate Transparency may be included in a | |
whitelist that Symantec will provide to Google. | |
Therefore, we will be sending you an individual email per customer | |
organization so that you can decide on behalf of each customer if you | |
want to whitelist their certificate information to maintain a good | |
Chrome browser experience for your customers’ websites. You can also | |
decide on not having the information whitelisted. | |
We need to receive your response on all the individual emails you’ll | |
receive by May 27th, 2016. | |
How do I Whitelist? | |
In order to whitelist your customers’ certificates, click on the link | |
on each email that you receive from Symantec and specify your | |
customer’s preference. | |
If you do not agree to include your customer’s unlogged SSL/TLS | |
certificates on the whitelist by May 27, 2016, all unlogged SSL/TLS | |
certificates not included on Symantec’s whitelist may trigger | |
“Untrusted” warnings in Google, Chrome and may cause operational | |
disruption. | |
Should you miss the May 27th, 2016 deadline, or if your customers’ | |
wish to change their CT preference to avoid “Untrusted” warnings from | |
occurring for a specified certificate, your customer will need to | |
replace, revoke and install a new SSL/TLS certificate. | |
For additional information related to Certificate Transparency, please visit: | |
Symantec | |
Thawte | |
GeoTrust | |
Best Regards, | |
Symantec Website Security Solutions | |
(*) [includes Symantec, GeoTrust, Thawte and RapidSSL brands] | |
This service message was delivered to as you are registered as a | |
Symantec customer, in order to provide you with account updates and | |
information about your account. | |
Symantec respects your right to privacy. See our Privacy Statement | |
If you have any questions or concerns, contact us at: Symantec - | |
Attention: Customer Support, 350 Ellis Street, Mountain View, CA | |
94043, USA | |
Copyright © 2016 Symantec Corporation. All rights reserved. Symantec, | |
the Symantec Logo, the Checkmark Circle Logo and the Norton Secured | |
Logo are trademarks or registered trademarks of Symantec Corporation | |
or its affiliates in the U.S. and other countries. Other names may be | |
trademarks of their respective owners. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment