Gogo injects false SSL certificates for google.com domains
1–10 of 52 posts
Re: Gogo injects false SSL certificates for google.com domains
#2Not condoning the practice, but thats my guess at the motivation. I also imagine it doesn't work very well, as many new browsers will refuse to display if the cert chain is broken.
Re: Gogo injects false SSL certificates for google.com domains
#3Random guess - this is probably because many people have a their homepage as a SSL'd google site. In order to be able to show the "login or pay" message to someone when they fire up their browser, Gogo needs to have a cert to communicate over 443 without the browser refusing to display a page. Not condoning the practice, but thats my guess at the motivation. I also imagine it doesn't work very well, as many new brows…
My guess is caching (thats in airplane).
Re: Gogo injects false SSL certificates for google.com domains
#4Re: Gogo injects false SSL certificates for google.com domains
#5I said this on reddit as well: could this just be them trying to block YouTube and other streaming services?
Re: Gogo injects false SSL certificates for google.com domains
#6Random guess - this is probably because many people have a their homepage as a SSL'd google site. In order to be able to show the "login or pay" message to someone when they fire up their browser, Gogo needs to have a cert to communicate over 443 without the browser refusing to display a page. Not condoning the practice, but thats my guess at the motivation. I also imagine it doesn't work very well, as many new brows…
My samsung tablet is aware of login and opens browser after it connects to wireless network. My guess is caching (thats in airplane).
Re: Gogo injects false SSL certificates for google.com domains
#7I said this on reddit as well: could this just be them trying to block YouTube and other streaming services?
Re: Gogo injects false SSL certificates for google.com domains
#8Re: Gogo injects false SSL certificates for google.com domains
#9I said this on reddit as well: could this just be them trying to block YouTube and other streaming services?
The certificate has SAN entries for things like google-analytics.com, android.com, *.cloud.google.com, goo.gl, g.co, urchin.com, and a plethora more[0].
If they wanted to just block YouTube, there are ways to do that without forging certificates. For example, modern browsers will send the domain name in plain-text even for HTTPS connections for SNI to function. They could easily block based on that.