Live data from Hacker News

Is Google overreaching by forcing me to use TLS?

security.stackexchange.com

21–30 of 37 posts

Re: Is Google overreaching by forcing me to use TLS?

#21
Best snarky answer from that thread: "Is Google overreaching by forcing you to log in with a password?"

Vaccine analogy answer from stackexchange: It's not just about you, it's about herd immunity. Having everyone have secure communications helps makes others secure as well.

Re: Is Google overreaching by forcing me to use TLS?

#22

I suppose it's nice to have the rationale written out somewhere, but does anyone anywhere actually balk at being required to use HTTPS?

Plausible deniability is frequently more useful then encryption. The probability of someone messing with my packets in-flight is low. But TLS creates the problem that you are possibly then able to prove that the packets I sent came from me.

Re: Is Google overreaching by forcing me to use TLS?

#23
post #22

I suppose it's nice to have the rationale written out somewhere, but does anyone anywhere actually balk at being required to use HTTPS?

Plausible deniability is frequently more useful then encryption. The probability of someone messing with my packets in-flight is low. But TLS creates the problem that you are possibly then able to prove that the packets I sent came from me.

This problem doesn't exist on the client side, no? It's not like we provide client certificates when using HTTPS/TLS. You're authenticating (typically) with passwords which unfortunately were stolen when your (random service goes here) account got hacked.

Re: Is Google overreaching by forcing me to use TLS?

#24

I suppose it's nice to have the rationale written out somewhere, but does anyone anywhere actually balk at being required to use HTTPS?

I realise I'm going to be in the 0.1% minority on this, but yep, I do. Three reasons.

First, I've been enough places where Internet connectivity is so poor that HTTPS effectively breaks the connection. I used to stay half the week somewhere where the only connectivity was a dire, over-saturated 3G link. I couldn't browse HTTPS sites unless I was very lucky.

Second, I'm uneasy with the implication that "HTTPS=secure", in that it absolves the user of taking any responsibility for their own security. A site can require a HTTPS connection and still store the password in cleartext, for example; so unless you have a unique password, this "secure" site can still screw you. Yeah, I know HN readers understand the difference, but IMX most people dimly understand a binary distinction between "secure site" and "not secure site" and that's it.

Third and related, the corollary of "HTTPS=secure" is that "sites that only use HTTP = insecure". This is leading to a requirement that any guy who builds a website with login functionality needs to implement HTTPS, and that saddens me. The web becomes less democratic, less meritocratic, the more technical hurdles we require.

But, like I say, I realise 99.9% of people disagree with me.

Re: Is Google overreaching by forcing me to use TLS?

#25
post #5

I agree with the overall point of the responses that Google isn't in fact evil to be doing this, but I want to disagree somewhat with one point - the idea that Google doesn't have any obligation to respect users wishes just because its a free service that no one is forcing you to use. The problem with this is that Google's very existence makes it harder for similar services to exist. There are a few reasons for this,…

Two points.

1. Google fought then-giants such as AltaVista, Excite and Yahoo in the process of establishing itself as the leader in search space. The incumbents had economies of scale and (relatively) massive amounts of data to crunch through. Yet a Google happened!

2. ``Google's very existence makes it harder for similar services to exist." History has proved time and again that such a premise is false. When it does become false, it is usually because of `dissimilar' disruptions in the landscape.

Re: Is Google overreaching by forcing me to use TLS?

#26
post #12

Uh, did this guy answer his own post?

You're encouraged to do that. I wonder why it seems to upset so many people? (I'm honestly curious, I'm not trying to be snarky)

Because the most obvious usage of such a feature is self-promotion.

Re: Is Google overreaching by forcing me to use TLS?

#27
post #2

A comment on the answer perfectly encapsulates this post: Did you just troll security.SE and then reasonably answer your own question? – Stephen Touset

If he didn't have a big reputation prior to this question, the comments would have been much harsher. There are people who ask and answer on their own for the sake of "reputation whoring".

Re: Is Google overreaching by forcing me to use TLS?

#28
post #25
post #5

I agree with the overall point of the responses that Google isn't in fact evil to be doing this, but I want to disagree somewhat with one point - the idea that Google doesn't have any obligation to respect users wishes just because its a free service that no one is forcing you to use. The problem with this is that Google's very existence makes it harder for similar services to exist. There are a few reasons for this,…

Two points. 1. Google fought then-giants such as AltaVista, Excite and Yahoo in the process of establishing itself as the leader in search space. The incumbents had economies of scale and (relatively) massive amounts of data to crunch through. Yet a Google happened! 2. ``Google's very existence makes it harder for similar services to exist." History has proved time and again that such a premise is false. When it does…

1. You are somewhat comparing apples to organges here. Google had access to the exact same websites as AltaVista, Excite, and Yahoo, so it's obvious that they could build an alternative search engine using the same data. But if you tried building an alternative email provider, you would not have access to the mails stored at google for training your spam filter.

2. You are contradicting yourself. "When it does become false" implies that it is true at some point, i.e., that there are hurdles to overcome, that is to say, that it is harder for a similar service to exist. Noone says that it is impossible, just that it is harder, and the form that that usually takes is precisely that it takes what you call "dissimilar disruptions" to establish an alternative. Having to come up with a "dissimilar disruptions" obviously is harder that coming up with some small evolutionary improvement.

Re: Is Google overreaching by forcing me to use TLS?

#29
post #5

I agree with the overall point of the responses that Google isn't in fact evil to be doing this, but I want to disagree somewhat with one point - the idea that Google doesn't have any obligation to respect users wishes just because its a free service that no one is forcing you to use. The problem with this is that Google's very existence makes it harder for similar services to exist. There are a few reasons for this,…

I think your reference to minimum wage is a little tenuous at best. The thing about technology is that it keeps progressing and eliminates barriers to entry. Yes, Google has a lot of machines, but now, without a lot of capital you can run a competing service without even having to own hardware. Yes, it's hard to write good spam filters, but Open Source Software allows you to get access to code that others have written which may be of similar quality, or at least give you a leg up on writing your own.

So yes, Google gets a temporary lock on mindset and technology, but as technology progresses there open up new opportunities to unseat the incumbents. If you'd asked anyone 10 or 20 years ago whether Microsoft could be unseated, they would have said you were crazy. The same goes for Google. With technology, nothing is permanent. Either you innovate, or you get left behind.

Re: Is Google overreaching by forcing me to use TLS?

#30
post #17

Can anyone explain this line from commenter Darren Cook: "Once this enforcement is in place, browsers will simply refuse to connect to Google over an insecure or compromised connection. By shipping this setting in the browser itself, circumvention will become effectively impossible." Some browsers are open source, and it seems to me that developers can never definitely rely on their behavior. Surely the enforcement d…

The point of TLS is to protect against MitM. The server refusing the non-TLS connection is not safe against MitM, a MitM can still claim to be the target server and accept the connection and thus (potentially) compromise the website/account/whatever. That is why the client has to refuse even trying to connect without TLS.
Post reply on HN