New Firedragon version!

It will most probably not going to be fixed.
When Fingerprinting is enabled, Floorp (or Firefox?) locks the UserAgent to

Mozilla/5.0 (Windows NT 10.0; rv:109.0) Gecko/20100101 Firefox/115.0

If you want to change the UserAgent, you have to disable Fingerprinting

and change the UserAgent to whatever you want:

1 Like

I followed the install to a T but noticed when it came down to the step 9, there was no /usr/lib/firedragon.cfg.pacnew and no indication of whether this is crucial or not? Is it?

I assume the old configuration is fine. What is the condition where that pacnew file would not be provided?

I already had disabled fingerprinting. It makes no difference. Also the radio toggle buttons for useragent don’t do anything, even though it saves the setting in the UI. I did edit firedragon.cfg to change it for real though. I have matched Firedragon’s settings to match my Firefox settings, including the exact useragent, have disabled the tracker blocking and uBlock Origin for the site, and Twitch still says my browser is unsupported. This seems crazy.

Same thing happened to me… no .pacnew. But I don’t think it’s that the old configuration is fine, I think it replaces the config file with the new one without doing a .pacnew.

It’s not important, if you don’t have it, then it’s all cool. I will edit my post.

The radio buttons won’t do anything with Fingerprinting enabled.
If you disable FP and it’s not ā€œreallyā€ disabled, then you are probably experiencing what I started to be convinced today: people need to install the new FD using a new Profile from scratch, just like if it was a new browser.

My own FD on my main machine had a LOCKPREF in about:config on the useragent, I couldn’t change it at all. I needed to start a new Profile and all is good now.
It seems some prefs get ā€œstuckā€ when installing over the same profile as old FD. The stuck prefs can happen at anytime and can be anything, I have seen a couple of variants already!

1 Like

Yes, I had to delete my profile and start from scratch. But I disabled Fingerprinting in the cfg file and the radio buttons still didn’t change anything. I had it set to Firefox but using a website that reports your useragent it still said Windows/Chrome.

Anyway, my point is, I have Firedragon reporting to whatismybrowser.com the exact same spoofed info as my Firefox… yet I can’t log into Twitch with it, while it lets me log in with Firefox just fine. I just don’t understand what else it could be detecting that’s different.

I noticed that whatismybrowser says (for me)

Your web browser looks like:
Firefox on Linux
But it’s announcing that is is:
Firefox 115 on Windows 10

which (I think) means a few things

  1. I probably have Firefox UA stuck somewhere in my old profile, it should at least report itself as Chrome on Windows (and I have another thing to look into)
  2. FPP and UA spoofing work… up to a point
  3. sites that go to great length to detect your browser (and no doubt there are ready made libraries to do just that) can still know that the UA is spoofed
  4. sites, and the external services like cloudflare that ā€œverify your connectionā€ (whatever that actually means), may consider it a sign of ā€œsuspicious activityā€ and act funny (refuse service, or simply have bugs in handling the different cases)

Spoofing a mobile UA works in the Floorp sidebar though: I put whatismybrowser there and

Firefox on Linux
Edge 114 on Android (Marshmallow)

and by the way, ā€œThird-Party Cookies are enabledā€ (but are they? are they supposed to be?)

I don’t know if maybe this can be used as a workaround to log in on pesky websites (and if it works, it means my theory is not the actual cause of problems)
I guess I’ll wipe the profile and re-import bookmarks and passwords to see if it makes a difference (but first I want to find why it’s spoofing the wrong UA)

2 Likes

Yeah, the default useragent spoof doesn’t fool that site. I put in a custom one to make it match the current Firefox and as far as I can tell, there is no difference. Every detail reported matches. Here’s the temporary link to my report:

(unrelated to the login problems, it’s about hardware acceleration)
Any chance of backporting this 1836021 - [Linux/VA-API] Force-enabling hardware decoding no longer works (FEATURE_FAILURE_VIDEO_DECODING_MISSING) ?

1 Like

Ok I understand. That’s good to know, we are trying to find the best balance of settings, not too strict but not too slack either.

There are various ways to troubleshoot this, what I’d suggest is to install FLOORP and try Twitch login right away without changing anything. If that works, good news we can probably find the setting and see if we should adjust it.
If the login fails, then I’m not sure we will slack settings more than FLOORP, or maybe it’s an internal issue with FLOORP in which case opening a bug on their github would be the way to go.

3 Likes

I have no idea if the Firefox fix is already in the version we use, maybe cuz I think it’s based on 115.6. If someone outside FF needs to do something more, then we rely on Floorp to patch stuff.
However I noticed 2 of the 3 settings are set to FALSE with our Release 10 here. I will set them to TRUE for next version.

1 Like

Amazing! That was very good advice. I installed Floorp and was able to log into Twitch with the default settings just fine. I changed a few more things in firedragon.cfg and was finally able to log into Twitch there also!

By trying to figure this out, my Firedragon security settings are actually weaker than the default Floorp settings… so now I will have to go through each setting one by one until I get blocked by Twitch again, so I can narrow down the actual thing they don’t like.

4 Likes

Excellent!
Plz report the final result here, we will see what action to take afterwards for the next FD version. :smiley:

3 Likes

Has anyone else noticed Dark Reader behaving very differently on some sites with the new Firedragon? It’s not a huge deal, but I’ve had to disable it or change it’s inversion mode on many sites where everything is now invisible or unreadable with the default settings. Very odd.

I have not noticed, can you get screenshots of examples?
If you don’t want to go back to old FD you can post a screenshot from the new FD and point out the differences.

1 Like

Sorry, I think that was a false alarm. I tried the sites I noticed it with on Firefox and Dark Reader looks the same. Just to be sure I installed Librewolf since that’s what old Firedragon was based on… and it’s also the same.

So either I am remembering incorrectly, or I had something set up differently before and forgot (I usually keep alternate dark mode extensions around for pages I can’t get Dark Reader to play nice with)… or something about the sites in question has changed recently. Either way, the new Firedragon isn’t behaving differently from the other browsers so it’s a non-issue.

1 Like

Version 14 is out!
See Post #1 for server link (it hasn’t changed).

This version fixes the PSD issue, in order to install it, after closing Firedragon, you have to do the following:

sudo rm /usr/share/psd/browsers/firedragon

And then install version 14 with only the pacman command

sudo pacman -U https://builds.garudalinux.org/chaotic-v4/garuda/x86_64/firedragon-11.7.1-14-x86_64.pkg.tar.zst

In this version some tweaks from @meanruse have been integrated and other details changed (no more centered URL and Bookmarks, fingerprinting enabled in Private Mode, no Parental Control, given user full control over FD (policy-wise)… little details like that. I couldn’t keep a changelog but will try to have a better one next times.)

12 Likes

FDG

Inspired by @FGD :slight_smile:

10 Likes

And I was thinking of trying Floorp cause I saw it being used by Chris Titus the other day…

Cause I mainly use brave, but it doesn’t play well with gtk lately for some reason. I’ve figured out a workaround but still gives me problems… Anyway

Thank you for this :blush::muscle:
Keep up the good work!!

2 Likes

Version 15 is out!
See Post #1 for server link (it hasn’t changed).

Changelog in firedragon.cfg:

  • LOCKWISE AND AUTOFILL section uses custom color for those who enable form Autofill (disabled by default)
  • Disabling Centered tabs/labels as I found out a visual glitch in one specific use case
5 Likes

Trying to catch up with Firefox release numbers, eh? :wink:

3 Likes