9 ms·
Google CA Root Inclusion Request
- artellectual 8y agoThis means we will get automated certificate issuing and renewal in google cloud? I’m looking forward to that.
- philipri 8y agoHeroku’s integration with Let’s Encrypt is pretty seamless (been using it for some hobby projects).
- emersonrsantos 8y agoIt's also seamless if you happen to use webmin, the open source "cpanel".
- TimTheTinker 8y agoWow, that’s still around? I last used webmin on a couple of servers 15 years ago.
- niftich 8y agoFor App Engine at least, they've offered this [1] for a year now; since 2017-09-14. [1] https://cloudplatform.googleblog.com/2017/09/introducing-managed-SSL-for-Google-App-Engine.html https://cloudplatform.googleblog.com/2017/09/introducing-man...
- zitterbewegung 8y agoStep One: Google becomes a CA with a large fanfair and covered in every tech blog Step Two: Google's entry makes the incumbents either decide to exit the space or change their bad behavior Step Three: Google exits the space accomplishing their mission and screwing over whoever uses their services. I really hope that it doesn't end like above but I think this will go the way of Google Fiber. Or maybe this is a play for their cloud services to also have be a CA like Amazon.
- magicalist 8y ago> Step Two: Google's entry makes the incumbents either decide to exit the space or change their bad behavior Yes, we wouldn't want the price of certificates to enter a race to the bottom. Let's Encrypt relies on that revenue! Honestly these comments...
- psergeant 8y agoThe comment you’re replying to thinks Step Two is good, but feels a bad Step Three is inevitable.
- magicalist 8y agoWhy would existing CAs leave the market if they didn't before?
- geofft 8y agoI think the argument is that existing CAs with mediocre practices are currently profitable, but in the presence of Google competition will stop being profitable and decide to exit, and may not decide to return if Google leaves. (I don't think the scenario as a whole seems likely, but this specific argument is analogous to e.g. concerns about Uber and Lyft competing with taxies on VC-subsidized pricing that will run out one day, or the loss of SF laundromats thanks to laundry startups.)
- magicalist 8y agoExcept, again, there are sponsored non-profits in this space. What further distortion do you expect?
- askmike 8y agoLE is great for a lot of things. But it doesn't offer the wide range of SSL certs everyone requires, such as OV and EV certs.
- scrollaway 8y agohttps://bugzilla.mozilla.org/show_bug.cgi?id=1325532 https://bugzilla.mozilla.org/show_bug.cgi?id=1325532 > Google Trust Services is run by Google. Google is a commercial CA that will provide certificates to customers from around the world. We will offer certificates for server authentication, client authentication, email (both signing and encrypting), and code signing. Customers of the Google PKI are the general public. We will not require that customers have a domain registration with Google, use domain suffixes where Google is the registrant, or have other services from Google. Finding the "email" bit interesting. All this makes a lot of sense, and I'd say I'm surprised this didn't come sooner but the initial issue was filed 2 years ago, and they must have worked on this for several years already then. As an aside this is a fascinating glimpse into what it takes to run a (serious) CA. https://static.googleusercontent.com/media/pki.goog/en/GTS-CP-1.0.pdf https://static.googleusercontent.com/media/pki.goog/en/GTS-C...
- TheSwordsman 8y agoThis URL 404s.
- tux3 8y agoTry: https://pki.goog/GTS-CP-1.0.pdf https://pki.goog/GTS-CP-1.0.pdf
- scrollaway 8y agoWeird. It needs the second slash. https://static.googleusercontent.com/media/pki.goog//en/GTS-CP-1.0.pdf https://static.googleusercontent.com/media/pki.goog//en/GTS-...
- zokier 8y agoI wouldn't read too much into the email part, that is pretty standard thing that pretty much all CAs do. I wouldn't expect Google to pursue email certificates in a major way. It's more like ticking a checkbox in the application and leaving that door open if the need arises. Also might be just some legacy from GlobalSign.
- geofft 8y ago
- ddtaylor 8y ago> Section 1.4.2 of the CPS expressly forbids the use off Google certificates for “man-in-the middle purposes” Uh huh.
- andrewstuart 8y agoThe recent flow of "Google is closing this service", followed by "Google is launching this new service" feels weird.
- niftich 8y agoThis submission's title was editorialized by the submitter. It was submitted as "Google CA", which is misleading, as the submission is about the preexisting Google CA's addition as a root CA in the Mozilla trust store. The article's underlying title is the more descriptive 'Google Trust Services Root Inclusion Request'. The Mozilla bugzilla issue [1] contains a more thorough picture of the process that went into considering these root CAs for inclusion in the Mozilla trust store, while the originally submitted URL [2] is focused on summarizing some of the background and rationale and inviting public comment. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1325532 https://bugzilla.mozilla.org/show_bug.cgi?id=1325532 [2] https://groups.google.com/forum/m/#!topic/mozilla.dev.security.policy/KYwIf67hcMg https://groups.google.com/forum/m/#!topic/mozilla.dev.securi...
- geofft 8y agoExcept that the application in the article contains the following statement: > Customers of the Google PKI are the general public. We will not require that customers have a domain registration with Google, use domain suffixes where Google is the registrant, or have other services from Google. This is not currently true of the existing Google root, and "Google CA" seems like an accurate-enough way of describing this change.
- nailer 8y agoSubmitter here, and yes exactly.
- dang 8y agoOk, we've changed the title to that of the page.
- nailer 8y agoAs geofft already points out, original title was accurate and new title removes the point. Dan how about you change it to: > "Customers of the Google PKI are the general public" From the actual article if you think "Google CA" is too short, or just restore the original title?
- psergeant 8y agoClicking on this is asking me to sign in...?
- adtac 8y agoDo you have JavaScript disabled? Don't you know we need JS to view nearly static mailing lists with minimal user interaction in 2018? /s
- jwilk 8y agoFor me, it shows empty page with JS disabled. Here's static HTML version: https://groups.google.com/forum/m/?_escaped_fragment_=topic/mozilla.dev.security.policy/KYwIf67hcMg https://groups.google.com/forum/m/?_escaped_fragment_=topic/...
- geofft 8y agoIt's Google Groups, which has weird behavior if you're somehow associated with a G Suite account that doesn't have Groups enabled. (My employer has some weird G Suite integration that prevents viewing public Google Docs, which has caused me to notice a few websites that are secretly just iframed Google Docs exports....) Try incognito/private browsing mode perhaps.
- zinssmeister 8y agoWe just published the “SSL wars” story between Symantec and Google https://www.templarbit.com/blog/2018/09/07/the-story-of-why-chrome-and-firefox-will-soon-block-sites-with-certain-ssl-certificates/ https://www.templarbit.com/blog/2018/09/07/the-story-of-why-... This adds another layer of color to that story.
- zokier 8y agoInitial Google Trust Services announcement discussion thread here: https://news.ycombinator.com/item?id=13494780 https://news.ycombinator.com/item?id=13494780 This has been brewing for quite a while now.
- rodgerd 8y agoNext: Chrome and Search privilege Google CA over others.
- anfilt 8y agoI really hate the current system of CAs. Google may act trust worthy, but I personally don't trust them. Same can be said of other CAs.
- dagenix 8y agoSo? Many people hate the current system. Its not clear that anyone has a better idea.
- nsgi 8y agoNow that we have Certificate Transparency you have much less need to trust them. Starting from scratch with a new system at this point would be a massive undertaking, all to attempt to solve a problem which has been largely fixed by CT.
- peterwwillis 8y agoTwo things which I think are technically possible with Google as a CA (please correct me if I'm wrong): 1) Google's new business in China enables Google to give China tools to inspect TLS traffic of arbitrary sites that use Google CA-derived certs 2) Google becomes a competitor to CloudFlare and uses position as CDN to inspect all encrypted traffic for data to mine, and then uses data to make more ad revenue (the way it does now with Gmail, search, etc)
- zackbloom 8y ago(which is something Cloudflare explicitly does not do)
- mmirate 8y agoThere's no way for anyone (other than Cloudflare's most trusted managers) to know that. All we know is it's somthing Cloudflare explicitly claims not to do.
- iancarroll 8y ago(1) is not technically possible unless Google issues new certificates for each site they want to inspect, and they would immediately be untrusted for doing so. (Admittedly, a CA did this once and is still alive, but they came very close to getting axed.)
- snaky 8y agoAnd that CA did it outside of China.
- tialaramex 8y agoI think your (1) makes it sound like more work than it really is What you'd do is issue a subCA, an intermediate certificate that says whoever has this key is allowed to issue more certificates, then you bake that subCA and the key into a MITM appliance. It mints the leaf certificates, in real time, when a connection happens. At the scale of a medium-sized corporation you can buy this off the shelf from a dozen or more companies, but obviously the off-the-shelf product produces untrustworthy certs. Usually what a business does is they set Windows Group Policy to say oh, actually we trust these bogus certs. They're supposed to mint a new key for this purpose, but I've seen big companies screw that up and trust the demo keys supplied with the product. This is fine because they're your machines, you set Group Policy. Don't want to trust dubious third rate "MITM appliances" from so-called security companies? Then don't add one in Group Policy. But if you gave these MITM appliances a "real" publicly trusted subCA they would work, and it would be seamless as far as ordinary Web users are concerned (it's not entirely undetectable, but no ordinary users would notice). It would definitely work for a fair-size company, or a small country. And maybe if you had the hardware and the money you could do it to, say, China, or America. We know TrustWave issued such a subCA to Walgreens, which caused a big fuss in 2012, and Mozilla told CAs that even though their policies had never specifically forbidden this it was a terrible idea, and they needed to confess and stop doing it. In 2013 the French government was caught doing this too, and their CA root was locked to ccTLDs controlled by France (France owns a bunch of quasi-independent little island nations with TLDs) in Firefox. In 2015 CNNIC did this "by mistake" selling a subCA to a company that, it says, didn't even want a subCA but just somebody screwed up. CNNIC was distrusted.
- exabrial 8y ago> These 4 roots were created by GlobalSign and then transferred to Google. Interesting, why would that happen? Why not generate the keys/certs yourself?
- nailer 8y agoCross signing allows support from older root stores.
- jhabdas 8y agoIs it just me or is Google Groups starting to look not much sleeker than the forums people used to self-host back in the mid-2000's?
- walterbell 8y agoRemember there is an AMP proposal for certificates to replace DNS for web site identity. In that scenario, Chrome would stop showing URLs and would only show the human-readable identity that signed the page, as validated by a certificate. This would allow signed site pages to be navigated offline or replicated widely or blacklisted :( There is a risk that Content IDentity would factor into EU upload filters and "link" taxes. History and Chrome demo video: https://news.ycombinator.com/item?id=17920720#17923156 https://news.ycombinator.com/item?id=17920720#17923156
- geofft 8y agoWhy is there more risk of sites being blacklisted with this model than with existing mechanisms? Google Safe Browsing can always ban your site. If you say "But people can turn off Safe Browsing," I'll counter with "But people can install their own CA."
- walterbell 8y agoIt's easier to move content to a new domain name than to a new legal identity.
- geofft 8y agoAnd certificates for webpackages attest domain name, not legal identity, right?
- walterbell 8y agoThey attest legal identity - watch the Chrome demo video.
- dredmorbius 8y agoThoughts occurring to me: browser devs (Chrome, Firefox, Safari, Edge) aready serve as a link in the CA trust chain, in that they can decert a CA. Browser dev as CA cuts out the middle man. Cutting out the midddle man removes a check on bad CA behaviour. I'm not sure where I stand on this, though I'm somewhat concerned.
- p0rkbelly 8y agoPretty sure this is fairly old, and pretty sure they are following Amazon's lead...almost literally via copy + paste(as an ode of approval and liking what they are doing) https://bugzilla.mozilla.org/show_bug.cgi?id=1172401#c9 https://bugzilla.mozilla.org/show_bug.cgi?id=1172401#c9
- BloodyHands 8y agoGoogle is an election fraud scam Google is not in a position to pretend it is a certificate authority
- acidtrucks 8y agoI wish x509 certificates had several CA signings. I would feel better n times better about a peer who has n unique validations. Every new CA that gets included just amplifies opportunities for coercion and blunder.