27 ms·
Chrome's Plan to Distrust Symantec Certificates
- ghostbrainalpha 9y agoIf you are using the free SSL provided your Webhost "Let's Encrypt" certificate, you will be fine. That is not a Symantec cert.
- wolco 9y agoWhen will google decide let's encrypt is not secure enough and start giving a warning around that.
- SteveNuts 9y agoConsidering Google is a major sponsor of the project, I'd say likely never. Not to mention that Google has been pushing hard for https on all sites, which is exactly LE's goal.
- problems 9y agoNot only that, but they're doing things like Certificate Transparency - publishing every certificate they sign into public logs and they're funded and supported by some of the biggest names in online security and privacy. They're probably the most trustworthy CA on the planet.
- peterwwillis 9y agoConsidering that literally anyone who gets even local access to any server at all, or can spoof one - even servers that have never used LetsEncrypt before - can generate new valid LetsEncrypt certificates, and nothing generated has a password on it, I don't know if I would consider them trustworthy. If you want to passively monitor encrypted traffic on a massive scale and not get caught (other than via their log - and who is reading that to see if every server they have has been issued a cert unnecessarily, anyway?), LetsEncrypt is awesome. It's plausible to do this without LetsEncrypt, but they made it a lot easier.
- gruez 9y ago>Considering that literally anyone who roots any server at all - even servers that didn't use LetsEncrypt before - can generate new valid LetsEncrypt certificates As opposed to any other CAs? There are plenty of other CAs that will happily grant a certificate if you prove control of a server that the domain resolves to. >nothing generated has a password on it, I don't know if I would consider them really trustworthy. If you have root on the server, can't you just dump the certificate out of memory, even if there's a password on it? short of using a HSM, you need the certificate decrypted so the server can use it.
- peterwwillis 9y agoWell I have a problem with the fact that you can't stop random CAs from issuing certs for a domain you own. But I don't think that's changing anytime soon. Passwords provide security for data at rest, a properly hardened server makes it very difficult to dump memory in certain circumstances, and hsm are practically a requirement in some environments. And finally, say I wanted to use LetsEncrypt, but I wanted to manage the keys myself, and require only private key X could be used to sign Y, and manage it myself. They don't really let me set those requirements at the CA level - it's all on my own host + network security, which IMHO is unnecessarily risky.
- detaro 9y ago> Another thing is, let's say I use some other CA for my certs, and I don't want LetsEncrypt issuing any. I can't really stop them, can I? CAA records. If you want full control over when issuance happens, you can even set the list of allowed CAs to empty and only change it when you actually want a certificate. > And finally, say I wanted to use LetsEncrypt, but I wanted to manage the keys myself If someone can submit a CSR and complete the challenges they get a signed cert, yes, just like with other DV-CAs. LE code (certbot or other clients) doesn't have to touch your private keys, as long as you give them CSRs, as with other CAs.
- pfg 9y ago> Another thing is, let's say I use some other CA for my certs, and I don't want LetsEncrypt issuing any. I can't really stop them, can I? You absolutely can. Let's Encrypt was one of the first CAs to support CAA (and, IIRC, they supported it when they first launched). CAA is a DNS record that lets you specify which CAs are permitted to issue certificates for your domain. > And finally, say I wanted to use LetsEncrypt, but I wanted to manage the keys myself, and require only private key X could be used to sign Y, and manage it myself. They don't really let me set those requirements at the CA level - it's all on my own host + network security. I'm not quite sure what you're saying here. Do you want the ability to issue certificates under your own (constrained) intermediate certificate? That's unfortunately not possible under the current Baseline Requirements unless you get audited as a CA. If you just want to use your own private key, that's of course possible (in fact, there's no way for Let's Encrypt to generate a key for you). Or is it that you want to limit limit issuance for domain X to key Y? What other CA allows you to do that? And how would you prevent some other CA from issuing a certificate for a different key, even if Let's Encrypt would support such a feature? With that in mind, it becomes clear that in the end it's up to your host and network security again, even with such an agreement in place.
- hollander 9y agoPushing TLS on all sites is only possible with free certificates. LE is essential. Nevertheless, never say "never".
- sofaofthedamned 9y agoWhen they do the stupid that other CAs have?
- agwa 9y agoExactly. And to be clear, the malfeasance by Symantec is voluminous and well-documented: https://wiki.mozilla.org/CA:Symantec_Issues https://wiki.mozilla.org/CA:Symantec_Issues Distrusting Symantec is not an arbitrary action as some people seem to believe.
- castis 9y agoProbably some time after Let's Encrypt shows some form of negligence while issuing certificates.
- 0xfeba 9y agoConsidering how bad these violations were, and how carefully FF and Chrome are documenting everything, I'd say about never.
- bitmapbrother 9y ago>When will google decide let's encrypt is not secure enough and start giving a warning around that When they start issuing illegitimate certificates.
- formula1 9y agofor a decentralized web - a way for people to be compensated for their time - mesh network - decentralized dns market - reservation system that supports known brands keeping their name - allows enough fluctuations that a name can be rereserved - opensource browser - keeping it simple enough for newbies to figure it out - a way to associate a public key to an IP address, reverify it and legitimize it - p2p shared files - trackers/dht torrent - decentralized hueristics - timelimit, algorithm fn, score fn, prize for heighest score
- dsp1234 9y ago"including Thawte, VeriSign, Equifax, GeoTrust, and RapidSSL" RIP RapidSSL wildcard
- _asummers 9y agoLE Wildcards should be around by then! Hopefully enough tooling will exist to make that migration seamless, or as seamless as cert migration can be.
- tomschlick 9y agoLE wildcards are coming early 2018 I believe so you'll still have a month or two gap.
- Guvante 9y agoNo action will be taken to impact users until March 15, 2018 at the earliest and only if you got your certificate before June 1, 2016. At least when it comes to any existing certificate (they are ambiguous about when they will cut off new certificates exactly).
- Ajedi32 9y ago> they are ambiguous about when they will cut off new certificates exactly They are? It seems pretty clear to me. Symantec's old infrastructure will be distrusted in Chrome beta in September 2018. At that point, no certificates issued by Symantec's old root certs (including those issued after June 1, 2016) will be trusted.
- Guvante 9y agoThey mentioned to not get any certificates from the old infrastructure after the new infrastructure is available as they will be untrusted earlier (to ensure that Symantec starts using the new infrastructure exclusively once it is available). However they didn't say when they would do that.
- deleted 9y ago[deleted]
- deleted 9y ago[deleted]
- agjacobson 9y agoOne of the happiest days of my life was when a Symantec support person, very courteously, helped me remove every Symantec product from my computer.
- leeoniya 9y agoi remember needing a util for this: https://support.norton.com/sp/en/us/home/current/solutions/v60392881_EndUserProfile_en_us https://support.norton.com/sp/en/us/home/current/solutions/v... was a key component of my debloating efforts back in the XP days.
- Joeri 9y agoNorton protect quietly reinstalled itself after I ran that tool. Oracle snuck it onto my system in a java update and I ended up having to dig through the registry and disk to weed it out. It is malware, plain and simple.
- dested 9y agoWhat could the lifetime value of a Norton customer be that they went to such incredible lengths to aquire?
- kuschku 9y agoQuite a lot, and it’s not just Norton. Google does the same, and pays companies to secretly include Chrome in their installers and auto-updaters, like they included the Google Toolbars before. Here’s an interview with the VLC developers, where the VLC developers complain how Google tried to get them to secretly install Chrome with it, and offered enormous amounts of money, but they obviously said no: https://www.youtube.com/watch?v=jWx1P93nS0c&t=48s https://www.youtube.com/watch?v=jWx1P93nS0c&t=48s
- timdorr 9y agoInteresting RCA from Symantec on the originating incident: https://bug1334377.bmoattachments.org/attachment.cgi?id=8831038 https://bug1334377.bmoattachments.org/attachment.cgi?id=8831... (PDF) Also, they provided several Q&A-style responses as well: https://bug1334377.bmoattachments.org/attachment.cgi?id=8831933 https://bug1334377.bmoattachments.org/attachment.cgi?id=8831... https://bug1334377.bmoattachments.org/attachment.cgi?id=8836487 https://bug1334377.bmoattachments.org/attachment.cgi?id=8836... https://bug1334377.bmoattachments.org/attachment.cgi?id=8838825 https://bug1334377.bmoattachments.org/attachment.cgi?id=8838...
- cperciva 9y agoI realize that the title here is what Google put on their blog, but it seems to me that "detrust" would be more accurate than "distrust".
- dragonwriter 9y ago“distrust” is an established English words that means exactly what Google intends. “detrust” is, while not hard to figure out, an unnecessary neologism.
- cperciva 9y agoBut "distrust" doesn't convey the full meaning. They're not talking about merely not trusting Symantec certificates; they're talking about removing existing trust in the certificates.
- frandroid 9y agoWhy create a new word when we can just add a new adjacent meaning to an existing nearby word...
- kronosEnvy 9y agoLanguage is mutable for this reason. If we didn't add any words but just kept using "nearby words" then we would be DANGER NO GO.
- cortesoft 9y agoIsn't 'removing existing trust' the same as 'distrust'? The word 'distrust' in no way implies that you have NEVER trusted them.
- dllthomas 9y ago"Distrust" doesn't imply that you have never trusted them, but it does allow for you never having trusted them, and so communicates less.
- mtgx 9y agoI want to thank the Chrome people that continued to investigate the initial issues with Symantec certificates rather than just take their word for it that it was a honest one-time mistake. I imagine there has been a lot of tension between Google and Symantec over the past year because of this, so it must not have been easy to keep poking at Symantec. After all, Symantec almost was one of the "too big too fail" CAs. Almost.
- ajr0 9y agoTo add to this sentiment. I think routine checks should done to all CAs, they are an important part of how "trust" works on the internet. and I see their importance only growing at this point. Google should not be the only company trying to enact change in this area. [edit: so many typos - oops]
- mintplant 9y ago> Google should not be the only company trying to enact change in this area. Fortunately they're not. Mozilla is involved here as well; just look at [0] and the other *.mozilla.org links in this thread. They also broke the WoSign/StartCom debacle. [0] https://wiki.mozilla.org/CA:Symantec_Issues https://wiki.mozilla.org/CA:Symantec_Issues
- chris_wot 9y agoNot just the Google Chrome guys, but also the Mozilla team who were also investigating a variety of issues.
- rand_r 9y agoAmusing that security.googleblog.com itself is using a TLS certificate ultimately signed by GeoTrust Inc, which is owned by Symantec.
- pfg 9y agoFun fact: one of the "independently-operated and audited subordinate CAs" that is exempt from this is, yep, you guessed it, Google. They've recently acquired a GlobalSign root and are in the process of getting their own roots added to trust stores, but I imagine they'll want to keep chaining back to the widely-trusted GeoTrust root for a few more years. (IIRC Apple is on that exception list too.)
- Ajedi32 9y agoActually, that subordinate CA isn't affected. See: https://chromium.googlesource.com/chromium/src/+/master/net/data/ssl/symantec/README.md https://chromium.googlesource.com/chromium/src/+/master/net/... And the blog post states: > This will affect any certificate chaining to Symantec roots, except for the small number issued by the independently-operated and audited subordinate CAs previously disclosed to Google.
- bitmapbrother 9y agoFormerly owned. They agreed to sell their certificate business to DigiCert.
- mixedbit 9y agoSurely the distrust doesn't apply to websites with the Norton Secured Seal, the most trusted mark on the internet: https://www.symantec.com/page.jsp?id=seal-transition https://www.symantec.com/page.jsp?id=seal-transition
- antihero 9y agoWhat are some trustable providers of EV certificates? LetsEncrypt is wonderful, but if I'm a company that needs to show the company name next to the padlock, who should I be using? What's an easy way to check if a provider (for instance Gandi, who I use for my domains) is going to be culled by this? In fact, I don't even seem to able to find certificate information in Chrome any more - clicking on the padlock just gives me a bunch of settings and "Learn more" which is some annoying page. Edit: It's in Developer Tools under "Security"
- driverdan 9y ago> I'm a company that needs to show the company name next to the padlock Does anyone actually look at or care about that?
- cpncrunch 9y agoYes, everyone who cares about their security when using online banking.
- rocqua 9y agoSee here [1] for a pretty good write-up arguing EV isn't worth much. One issue is that it only has value if you would notice it is missing. Would you trust a paypal site that just had the green padlock, but not the name? Do you think your parents would? [1] https://www.troyhunt.com/journey-to-an-extended-validation-certificate/ https://www.troyhunt.com/journey-to-an-extended-validation-c...
- snuxoll 9y agoIt's useful for no-name companies, an EV certificate highlights a company that went through unnecessary pain just to get a little green checkbox - I know I personally trust smaller online retailers more when they have one since they've had to prove their identity to a CA. Nobody notices the lack of EV on amazon.com, because, well, it's Amazon.
- 9y ago
- mrkidd 9y agoIs there a list somewhere of the actual Root CA certificates that will be removed as part of this? Is it just any Root CA certificate that has "Symantec, Thawte, VeriSign, Equifax, GeoTrust, and RapidSSL" in it's name?
- jakelazaroff 9y agoIs there a list of CAs that will be affected? I can't find a link to one in the article.
- jlgaddis 9y agocf. https://news.ycombinator.com/item?id=15222517 https://news.ycombinator.com/item?id=15222517, per Ajedi32.
- jakelazaroff 9y agoThanks!
- grandalf 9y agoI wish browser vendors would let me choose a trusted entity and make it simple for me to trust only CAs that my trusted entity supports, or the intersection of what multiple trusted entities endorse. The incentive for a mass-market browser is to trust pretty much everything, but I'd prefer to use a browser that is a bit more paranoid. If a website can't load properly because I don't trust one or more of the CAs, I might want to temporarily "live dangerously" but would be a bit more cautious about typing data into a form, etc. Browser vendors should not try to create a one-size-fits-all list of trusted CAs, since there is obviously a very different level of trust deserved by various CAs based on the track record of each one. If I were a state actor intelligence agency, compromising CAs would be toward the top of my list because of the amazing opportunity for man-in-the-middle attacks. Distrusting Symantec certificates is a great step in the right direction.
- hiram112 9y agoExactly. I've never understood why all the US / EU language versions of Chrome, Firefox, etc. include all the root certs for CAs from China, Turkey, Russia, etc. I cannot read Mandarin or Turkish, and in the unlikely event I get forwarded to a site from a company targeting citizens from these countries, I'd prefer to just get an SSL exception instead of the 'trusted' page.
- nl 9y agoWhat about the huge number of English language Chinese run ecommerce sites? Why should they be discriminated against because of their native language? That just makes the normal user who wants to buy stuff learn to ignore SSL errors.
- hamandcheese 9y agoIs it unreasonable to expect a foreign ecommerce site to use a CA that it's users can trust?
- nl 9y ago
- gscott 9y agoComodo is giving away free Certificates to Symantec customers https://www.comodo.com/Google-Chrome-announces-proposal-to-distrust-certain-Symantec-certificates/index.php https://www.comodo.com/Google-Chrome-announces-proposal-to-d...
- rallison 9y agoFor those considering Comodo, I'd ask that you reconsider. They tried to trademark LetsEncrypt: https://news.ycombinator.com/item?id=11964583 https://news.ycombinator.com/item?id=11964583 https://news.ycombinator.com/item?id=11973232 https://news.ycombinator.com/item?id=11973232 Bad OCR led to certificates being issued to the wrong people: https://news.ycombinator.com/item?id=12761248 https://news.ycombinator.com/item?id=12761248 They created their own Superfish-like adware: https://news.ycombinator.com/item?id=9091917 https://news.ycombinator.com/item?id=9091917
- MertsA 9y agoDon't forget Chromodo which was a reskin of Chrome with --disable-web-security set. Because that totally makes their browser super secure!
- kccqzy 9y ago> This plan, arrived at after significant debate on the blink-dev forum, would allow reasonable time for a transition to new, independently-operated Managed Partner Infrastructure while Symantec modernizes and redesigns its infrastructure to adhere to industry standards. It's funny they still mention giving Symantec an opportunity to modernize and redesign its infrastructure when Symantec simply decides to give up: http://investor.symantec.com/About/Investors/press-releases/press-release-details/2017/DigiCert-to-Acquire-Symantecs-Website-Security-and-Related-PKI-Solutions/default.aspx http://investor.symantec.com/About/Investors/press-releases/... Interestingly, this investor.symantec.com doesn't properly support HTTPS at all (certificate host name mismatch). I guess that speaks volume about how much Symantec itself cares about SSL/TLS and PKI.
- Drdrdrq 9y agoWise actually. This way nobody can say that they were being unfair to Symantec, and it costs them nothing. They can still decide either way.
- naraniano 9y agoReminder: on Chrome, when a website displays an SSL warning, you can type "badidea" to bypass it.
- JoelJacobson 9y agoSWIFT is the only single entity trusted by all banks in the world. I think they would be a perfect fit for a CA to issue online banking certificates, since there is no way to get around trusting SWIFT as a bank, so they might as well trust them for their certificates as well, instead of trusting Symantec or any other CA. The less entities you have to trust, the better.
- DaiPlusPlus 9y ago> since there is no way to get around trusting SWIFT as a bank I understand banks are free to have some kind of direct-transfer mechanism between them, like internet peering, it would just be redundant. But anyway, I would not trust SWIFT as gatekeepers of banking security. They're a prime example of a business that runs on COBOL written 40 years ago and they're not the paragon of progressive thinking in banking (SWIFT could torpedo Western Union overnight if they really wanted to) and finally, they already have a poor reputation in INFOSEC circles: https://en.wikipedia.org/wiki/2015%E2%80%932016_SWIFT_banking_hack https://en.wikipedia.org/wiki/2015%E2%80%932016_SWIFT_bankin...
- pebers 9y agoAka. putting all your eggs in one basket... Banks shouldn't be relying on outdated infrastructure providers to do things they aren't good at. The sensible thing (and indeed more or less what happens now) is for banks to choose a best-of-breed CA to issue SSL certs, the same way any other company offering sensitive services over the Internet would do it.
- e12e 9y ago> Aka. putting all your eggs in one basket... To a certain extent the alternative here is to put all your eggs in all the baskets - if an elephant steps on any one of the baskets the eggs (your security) breaks...
- infinity0 9y agoThat's really not good security logic. It's better to trust a very strong entity for 1/2 of your security and a weak entity for the other 1/2, so that when shit breaks you at least have a more accurate suspicions on which part of your system broke, to start the investigations from. It's much worse to trust a single weak entity for 1/1 of your security. That said, it's possible SWIFT can be a good CA. But you shouldn't choose them if they do a crap job of it, simply to "reduce the number of entities you trust".
- riquito 9y agoI understand that the solution is complex, but until 17 April 2018 my browser is going to accept some certificates that are reputed to be unsafe today. If this is the power that the browsers have over CA I don't feel secure.
- dpacmittal 9y agoSlightly offtopic but still related to web-security in general; how can I be sure about chrome extensions that I'm using are not doing malicious stuff? I think if a state actor or a resourceful entity wishes to steal data of users, attacking/hijacking/buying a popular chrome extension would be so much easier than attacking a CA or doing MITM over SSL, and trying to decrypt it. I've always hated the concept of certain chrome extensions having full access to all the pages I visit in the browser but sometimes its necessary. Ad blockers are way too high on the list of potential attack targets, close second would be web development extensions like editthiscookie. There needs to be a way for webpages to indicate that they don't want any external scripts running on the page. Even a setting in chrome would be really helpful. I don't want external scripts to be running on my bank website, or when I'm working with my stock exchange website. Right now I'm making do with multiple chrome profiles but that doesn't cut it. There needs to be some initiative in this regard from major browser vendors.
- mehrdadn 9y agoYes, I agree. The possibility of a rogue extension stealing data also freaks me out. All you need is the Google account of 1 popular extension's author to be hijacked, and now the person has full control over all the credentials of every user of that extension within an hour or so. I was so concerned about this potentially ticking time bomb, in fact, that I sent an email about this to a prominent person on Chrome's security team many months ago. I did not receive a reply.
- Dylan16807 9y agoFor web pages to indicate? No, that'll get attached to every terrible ad in the world.
- dpacmittal 9y agoYes, that would actually do more harm than good, but no reason to not provide a setting where user can add to the list of URLs similar to what chrome is already doing for flash, notifications, location, camera etc
- 9y ago
- Buge 9y agoAnother potential problem for people who pinned certs. There should be a standard to pin EV-ness. That way you know all certificates for your site have been issued by an audited process and not by dns hijacking.