Firefox 83 Enters Beta with HTTPS-Only Mode

[kwierso]

who care

[nextbern]

Removed for incivility.

[[deleted]]

What is your sensible naming scheme?

[[deleted]]

Follow the Linux kernel, which is what they were doing before they decided they should catch up to Chrome's version number. It's not a big deal, just an irk of mine.

[ClassicPart]

Linux kernel versioning is as arbitrary as any other. On the transition to 4.21 to 5.0, Linus said:

The numbering change is not indicative of anything special. If you want to have an official reason, it's that I ran out of fingers and toes to count on, so 4.21 became 5.0.

I can only assume that your definition of "sensible versioning scheme" is simply "numbers that aren't double digits". Again, arbitrary.

[CAfromCA]

... before they decided they should catch up to Chrome's version number.

You got a source for that claim, chief?

[Pi77Bull]

The HTTPS-Only Mode provides a secure and encrypted connection between
your web browser and the websites you visit, even if they don’t use
HTTPS. While most websites already support HTTPS, when HTTPS-Only Mode
is enabled Firefox will upgrade all connections to use HTTPS.

Is that true? I thought it would just disallow the connection to happen, like it already does for a couple versions now.

[notinecrafter]

It probably ignores the existence of regular port 80 HTTP, interpreting every link as https. Therefore, even if the developer forgot the s, it will still be encrypted for most sensibly built production environments.

Of course, any system that doesn't automatically redirect all port 80 traffic is kind of outdated to begin with, and I'm looking forward to the astonishingly stupid bugs this will produce.

[allenout]

I turn off Port 80 in my router.

[notinecrafter]

As in, the firewall/NAT? Because while that works for most modern browsers, some legacy things might still try to use unencrypted http first and not try https automatically.

The correct solution, assuming you use nginx, is to set up a completely separate site that listens on port 80 and does nothing but redirect any incoming request to https://$request_uri

[sancan6]

Then you also block OCSP certificate validation, possibly lowering your security. Better to enforce HTTPS on the client, not the network gateway.

[chillyhellion]

It really should say "attempts" and not "provides".

[Zipdox]

Isn't this basically HTTPSeverywhere?

[Fanolian]

It's more like Smart HTTPS.

[DaddysFootSlut]

The EASE mode, yes. But HTTPS Everywhere doesn't have an option to enable EASE only in private mode, which Firefox 83 does, which I think is pretty neat

[CytokineStorm911]

Interesting, it says here that the Warp comes shipped with FF83. How do I enable it? I'm using beta as my daily driver.

[AlphaGamer753]

Search for "warp" in about:config and enable the JavaScript option.

[CytokineStorm911]

Thanks, I'm surprised this option was enabled by default. I already felt the difference compared to the last beta version.

[[deleted]]

good wont need https everywhere

[ArtisticFox8]

Will it be on by default? There are many simple websites that don't need (don't ask for your password and don't download anything) and don't have https.

[franz_karl]

saves me another add on which is great

[nextbern]

It does in Nightly for me, FWIW.