Live data from Hacker News

HTTPS by default

security.googleblog.com

121–130 of 268 posts

Re: HTTPS by default

#121
post #27

Earlier quoted context omitted.

There are good arguments for it, but it's also not a coincidence that they happen to align with Google's business objectives. Ex it's hard to issue a TLS cert without notifying Google of it.

I don't get your logic/reasoning here... could you explain?

There are public logs of every TLS cert issued by the major providers. This benefits Google.

Kinda like how Wikipedia benefits Google. Or public roads benefit Uber. Or clean water benefits restaurants

Re: HTTPS by default

#122

Earlier quoted context omitted.

Devil's advocate, but maybe ISPs should all inject ads to make a point. They make money, and anyone using HTTP gets taught a free lesson on what MITM means

Before turning on the dude who thrives to keep the internet free, fix your corporate laptop that does MITM even for HTTPS connections.

I own a personal laptop?

Re: HTTPS by default

#123
post #113

Https really sucks for our intranet. Every little web app and service needs certificates and you can't use letsencrypt.

You may not want to, but you can use public certs and URLs on your intranet. You can't necessarily do http-01 challenges, but DNS based challenges are feasible. There are also other ACME providers which will let you skip challenges for DCVd domains.

Re: HTTPS by default

#124
post #21

Earlier quoted context omitted.

Depend on one less third party, you still depend on the DNS Root servers, your ISP / hosting, domain registry, etc.

Let's Encrypt pushes me to run its self-updating certbot on my personal server, which is a big no-go. I know about acme.sh, but still...

I counted by hand, so it might be wrong, but they appear to list and link to 86 different ACME client implementations across more than a dozen languages: https://letsencrypt.org/docs/client-options/

I've used their stuff since it came out and never used certbot, FWIW. If I were to set something up today, I'd probably use https://github.com/dehydrated-io/dehydrated.

Re: HTTPS by default

#125
Prediction: Wifi captive portal vendors will not react to this until after 90% of their customerbase has their funding dry up.

It is incredibly common for public wifi captive portals to be built on a stack of hacks, some of which require the inspection of HTTP and DNS requests to function.

*Yes better tools exist, but they dont arent commonly used, and require Portal, WAP and Client support. Most vendors just tell people to turn new fancy shit off, disable HTTPS and proceed with HTTP.

Re: HTTPS by default

#126

Prediction: Wifi captive portal vendors will not react to this until after 90% of their customerbase has their funding dry up. It is incredibly common for public wifi captive portals to be built on a stack of hacks, some of which require the inspection of HTTP and DNS requests to function. *Yes better tools exist, but they dont arent commonly used, and require Portal, WAP and Client support. Most vendors just tell pe…

To be fair, most people connecting to captive portal networks are more likely to be doing so on their phones, and I don't think IOS even allows non-Safari browsers for captive Wi-Fi login. I'm unsure how they'll fix this for Android though.

Re: HTTPS by default

#127
post #25

Earlier quoted context omitted.

There are dozens of us I guess that care about this kind of thing. I have never really understood the obsession with https for static content that I don't care if anyone can see I am reading like a blog post. HTTPS should be for things that matter, everything else can, and think should use HTTP when it is not necessary. Depending on yet another third party to provide what is IMHO a luxury should not be required, and…

It’s static while you control it. Soon as I MIIT your content it will look to your users like you updated your site with a crypto miner and a credit card form. You can publish your site with a self-signed key if you’d like and only depend on your ISP/web host provider, DNS provider, domain registrar, and the makers of your host OS and web server and a few dozen other things.

> MIIT

Man in in the?

Re: HTTPS by default

#128
post #58

Earlier quoted context omitted.

It doesn't MITM anything. Do you see that as normal? Because I don't. We're adults here and I'm a tech guy, there's zero reason to control anything in my laptop. In fact it's just a regular laptop that I fully control and installed from scratch, straight out of Apple's store. As all my company laptops have been. And if it was company policy I would refuse indeed. I would probably not work there in the first place, hu…

My work laptop has a CA from the organization installed and all HTTP(S) traffic is passed through a proxy server which filters all traffic and self-signs all domains with its' CA. It's relatively common for larger organizations. I've seen this in govt and banking.

To provide a European/Dutch perspective: I’m pretty sure that as a small employer myself, I am very much disallowed from using those mechanisms to actually inspect what employees are doing. Automated threat/virus scanning may be a legal gray zone, but monitoring-by-default is very much illegal, and there have been plenty of court cases about this. It is treated similarly to logging and reading all email, Slack messages, constantly screenrecording, or putting security cameras aimed at employees all day long. There may be exceptions for if specific fraud or abuse is suspected, but burden of proof is on the employer and just monitoring everyone is not justifiable even when working with sensitive data or goods.

So to echo a sister comment: while sadly it is common in some jurisdictions, it is definitely not normal.

Re: HTTPS by default

#129

Earlier quoted context omitted.

Main reason is that it's hard to get certificates for intranets that all devices will properly trust. Public CAs don't issue (free) certificates for internal hostnames and running your own CA has the drawback that Android doesn't allow you to "properly" use a personal CA without root, splitting it's CA list between the automatically trusted system CA list and the per-application opt-in user CA list. (It ought to be n…

If someone is in your LAN then you have bigger problems than them snooping on you while you talk to your fridge.

Like eBay? Slightly different https://nullsweep.com/why-is-this-website-port-scanning-me/

Re: HTTPS by default

#130

Earlier quoted context omitted.

It’s static while you control it. Soon as I MIIT your content it will look to your users like you updated your site with a crypto miner and a credit card form. You can publish your site with a self-signed key if you’d like and only depend on your ISP/web host provider, DNS provider, domain registrar, and the makers of your host OS and web server and a few dozen other things.

> MIIT Man in in the?

Typos happen :)
Post reply on HN