Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox 67.0 Released

mozilla.org

Post reply on HN
Print view View original

131–140 of 264 posts

Re: Firefox 67.0 Released

#131

Post by radcon »

danShumway wrote: post #94
radcon wrote: post #65

I can't find much info on the fingerprint protection. Has anyone tested it thoroughly? Do we know if it's effective against current fingerprinting methods? Can we actually rely on it, or will it simply be a matter of days/weeks before websites adapt to defeat this protection?

I don't think it's sufficient yet to stop someone determined, but I do think it's a step in the right direction, particularly when combined with a VPN. I'm looking forward to the letterboxing improvements. Anecdotally, I get a lot more captcha's when it's turned on. I regularly log in to sites and get prompts telling me I need to enter email confirmation codes. I signed up for a service recently that auto locked my a…

I agree, those are good signs.

If these fingerprint protection tools are effective, my main fear is that websites will simply say "Disable your fingerprint protection if you want to proceed", much like many sites currently do with ad blockers. Or if they don't spell it out in plain English, they'll make you jump through so many hoops that you'll switch it off just to end the suffering.

Trying to interact with any major website using the TOR browser has been a complete nightmare. If you aren't blocked outright, you face CAPTCHAs at every turn.

Re: Firefox 67.0 Released

#133

Post by kpremote »

Apologize if this is not the right place to ask for help.

Two days ago when I began to develop a web site backend, a strange thing happened. Visiting "mydomainname.com" in Firefox v66 gave me back error message saying site not found, but visiting "mydomainname.com/index.html" (or index.php) would be fine, the content of that page was returned.

After one hour struggle, I used another browser (and my phone) to open "mydomainname.com", and it worked fine! It returned the index.html page. So it's not the issue of the default file setup.

Did I miss something obvious? I felt stupid. I am now using Chrome but I would like to come back to Firefox. Thanks for any help.

Re: Firefox 67.0 Released

#134

Post by rasjani »

jobigoud wrote: post #73
cesarb wrote: post #24

> Change to extensions in Private Windows: Any new extensions you add to the browser won’t work in Private Windows unless you allow this in the settings. Does this mean that adblocking (and other safety-related) extensions will suddenly stop working on private windows, unless the user knows it has to go to the settings and enable them again?

I'm interested in the rationale behind this default. What about extensions make them a possibly bad fit for incognito mode?

What addons are installed is one criteria of bowser fingerprinting.

Re: Firefox 67.0 Released

#135

Post by geofft »

lholden wrote: post #43
akavel wrote: post #39

> "Enable FIDO U2F API, and permit registrations for Google Accounts" Oh! Didn't expect that! Does this mean YubiKeys will now be working in GMail on Firefox? Together with all the other stuff, this starts to look like a really important and major release of Firefox.

Yep, though technically one could enable this before now by tweaking the about:config security.webauth.u2f setting. (Which is something I've been having to do for a while now). As a side note... the way Google handles U2F is somewhat out of spec. For example, you haven't been able to register a u2f device with Firefox on google. I wonder if that's been worked around with this release? That would be great! Otherwise,…

Yes, that's what they worked around in this release and you can now register a U2F device with Firefox for Google Accounts. See their announcement blog post https://blog.mozilla.org/security/2019/04/04/shipping-fido-u... and the mozilla.dev.platform Intent-to-Ship post: https://groups.google.com/forum/#!msg/mozilla.dev.platform/q...

tl;dr (as I understand it): existing Android phones using NFC/Bluetooth U2F devices only speak the old U2F protocol, not WebAuthn, so if Google switched to WebAuthn registration, then you wouldn't be able to log into your account on Android, and they want to wait until all those Android devices die off. (Apparently it's in the part of Android that needs vendor updates, not in Google Play Services, so this reduces to the previously unsolved problem of Android OS updates on old devices.)

Re: Firefox 67.0 Released

#136

Post by geofft »

will4274 wrote: post #119
akavel wrote: post #39

> "Enable FIDO U2F API, and permit registrations for Google Accounts" Oh! Didn't expect that! Does this mean YubiKeys will now be working in GMail on Firefox? Together with all the other stuff, this starts to look like a really important and major release of Firefox.

This is an anti-feature. Firefox enabled a deprecated standard because Google couldn't be bothered to move to the current standard. Classic catering to the big players.

They held off for a very long time, and I'm glad they did that. I'm also glad they switched, because the alternative is that either you don't use the most effective security option available or you stop using Firefox, both of which seem like even bigger long-term problems.

Re: Firefox 67.0 Released

#137

Post by lugg »

backpackway wrote: post #9

> Save passwords in private browsing mode While this might be handy when visiting your favorite paid porn site, isn't this counter-intuitive? When I am in private mode, I expect nothing to be saved.

Sounds like we need a guest mode where nothing saves but add-ons work and a privacy mode where things are privacy driven and only certain add-ons work.

Re: Firefox 67.0 Released

#138

Post by groovybits »

callahad wrote: post #101
stevekemp wrote: post #52

When I upgraded from 66.0.5 it created a new profile, rather than keeping my existing passwords/histories/extensions. I'm not going to use firefox sync, so it seems like there will be a painful migration ahead.

We're defaulting to profile-per-install to make it easier to run different versions side-by-side, but you can still manually specify your original profile. Docs on the profile manager are at https://support.mozilla.org/en-US/kb/profile-manager-create-... ...or, as a super weird hack, you can set the envvar SNAP_NAME=firefox to get the old behavior (see https://github.com/mozilla/nixpkgs-mozilla/issues/163 for context…

Just curious, how large is the benefit of this? Does the average user run multiple versions of Firefox side-by-side?

I consider myself a power user in many things, but never have I felt the need to run different versions of my browser simultaneously.

Re: Firefox 67.0 Released

#140

Post by johnp_ »

gerbilly wrote: post #6

I tried to see if letterboxing was enabled, but it didn't seem to make a difference.¹ Does anyone know whether they included this feature, and if so how to enable it? 1: https://browserleaks.com/javascript still detects my window size down to the pixel.

`privacy.resistFingerprinting.letterboxing` is currently a separate setting since it's still rough around the edges. Not sure if it works on Release, I have it set on Nightly.
Post reply on HN