Firefox 83 introduces HTTPS-Only Mode

Post by a1369209993 » Tue, Nov 17, 2020, 7:20 PM UTC

kibwen wrote: post #375

shadowgovt wrote: post #335

Earlier quoted context omitted.

Agree to disagree. I've met enough Americans to believe that if we made voting mandatory, we'd just end up with Optimus Prime at the top of the ticket. You can make an act compulsory on the whole population but you can't legislate duty-of-care upon the whole population.

Voting should be mandatory but the first listed option for every office should be "I approve of no candidate and think none of them should win" (the disaffected vote), and the second listed option should be "I approve of every candidate and don't care who wins" (the apathetic vote). With our current system it's impossible to tease out how many voters are disaffected vs apathetic vs simply disenfranchised (in the abov…

Post by minitech » Tue, Nov 17, 2020, 7:27 PM UTC

kazinator wrote: post #386

What I don't understand is why there isn't a simple button when you land into a HTTP page to switch to HTTPS. In the browser bar, to the left the address, you get an icon of a padlock, with a red slashed circle across it, and the word "Not secure". Why can't you click on this to get a popup to switch to trying the HTTPS version of the URL? You can click on it, you get to a read-only tree of information providing info…

Post by manquer » Tue, Nov 17, 2020, 7:35 PM UTC

bscphil wrote: post #409

manquer wrote: post #406

Earlier quoted context omitted.

If you follow the DNS specs this will not a problem. If you use *.local for local domain names DoH will never be triggered From Mozilla documentation. "localhost" and names in the ".local" TLD will never be resolved via DOH. [1] Lan based services are pretty common use case. Mozilla is hardly going to release this feature without considering this. The Cloudflare / Archive.is point is esoteric debate and not a common…

> If you follow the DNS specs this will not a problem. If you use *.local for local domain names DoH will never be triggered I don't think PFsense + Unbound supports appending .local to every hostname automatically, so I'd have to change every last one of my hostnames to whatever.local and that seems like a real pain. (Surely most people are not using whatever.local in their /etc/hostname, right?) > The Cloudflare /…

Post by cptskippy » Tue, Nov 17, 2020, 7:36 PM UTC

emn13 wrote: post #337

cptskippy wrote: post #289

Earlier quoted context omitted.

> None of this - DoH, nor HTTPS-only - is required. It's not even on by default (yet). I had to disable DoH on all 5 of my machines because it was enabled automatically. > You mention pihole; and though I've never used it, they do have a page on DoH pihole supports using Cloudflare as an upstream DoH provider, not acting as a DoH provider.

> I had to disable DoH on all 5 of my machines because it was enabled automatically. Some googling: it's on by default in the US now, not yet globally. > pihole supports using Cloudflare as an upstream DoH provider, not acting as a DoH provider. That's unfortunate; are you sure it's not just a little poorly documentend? At least the underlying software they link to https://developers.cloudflare.com/1.1.1.1/dns-over-h…

Post by TheRealPomax » Tue, Nov 17, 2020, 7:38 PM UTC

iso1631 wrote: post #87

jchw wrote: post #18

I’m surprised at the negative knee-jerk reaction. I actually love this idea immediately. It encapsulates something I kind of already wanted when using HTTPS Everywhere. This doesn’t guarantee the transport is end-to-end secure; I’m sure plenty will strip the encryption at an LB and then possibly send it back over the internet. But, I think it’s a good addition nevertheless. Here’s to hoping for more DoH and encrypted…

I want my OS to do DNS - including DOH, not my browser. I want a single source for my DNS I want my network to tell me a DNS server to use. As I own my computer I can override that, but much of the time I want to use the network provided DNS server.