9 ms·
I've been through all of Firefox `about:config` a few times in the past, fixing preferences to, e.g., try to disable umpteen different services that leak info o
by neilv 8y ago
I've been through all of Firefox `about:config` a few times in the past, fixing preferences to, e.g., try to disable umpteen different services that leak info or create potential vulnerabilities gratuitously, but this is the first I recall hearing of Normandy.
Apparently I missed `app.normandy.enabled`, because I think I would've remembered a name with connotations of a bloody massive surprise attack.
Incidentally, `app.normandy.enabled` defaults to `true` in the `firefox-esr` Debian Stable package. Which seems wrong for an ESR.
For personal use (not development), I run 3 browsers (for features/configurations and an extra bit of compartmentalization): Tor Browser for most things, Firefox ESR with privacy tweaks for the small number of things that require login, and Chromium without much privacy tweaks for the rare occasion that a crucial site refuses to work with my TB or FF setup.
Today's crucial cert administration oops, plus learning of yet another very questionable remote capability/vector, plus the questionable preferences-changing being enabled even for ESR... is making me even less comfortable with the Web browser standards "big moat" barrier to entry situation.
I know Mozilla has some very forthright people, but I'd really like to see a conspicuous and pervasive focus on privacy&security, throughout the organization, which, at this point, would shake up a lot of things. Then, with the high ground established unambiguously, I'd like to see actively reversing some of the past surveillance&brochure tendencies in some standards. And also see some more creative approaches to what a browser can be, despite a hostile and exploitive environment. Or maybe Brave turns out to be a better vehicle for that, but I still want to believe in Mozilla.
- robolange 8y agoI too use Debian's Firefox ESR. I noticed the "Allow Firefox to install and run studies" option in Privacy & Security Preferences a long time ago. It was unchecked and greyed out (i.e., unclickable), and a label below it says "Data reporting is disabled for this build configuration", so I gave it no further thought. This morning I woke up and launched Firefox, noticed this headline, and then noticed my extensions were still running. I looked in about:config and lo and behold, app.normandy.enabled=default [true]. I'll be filing a bug with debian to disable this in the build configuration. Edit: There are some questions about whether Normandy is really enabled in Debian Firefox ESR even if the about:config setting defaults to true. I've filed a bug report, and I'm sure once a Debian maintainer has a chance to look at it we'll find out the answer. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928433 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928433 Edit2: It should go without saying, but please do not spam this bug report with "me too" and its ilk.
- bilbo0s 8y agoI had mine disabled. So let's think about this for a second. If I disable a security hole that you can drive a semi-truck through, I remain foobar'd. If I run my "secure" firefox configuration, with the security hole enabled, then they un-foobar me first. Before anyone else. So I could effectively get rewarded, for always keeping a security hole open. But I didn't keep it open, so... yeah... they'll get around to me sometime. ? >:-( Grrr. I'm just getting old and curmudgeonly maybe? I've decided though, I'm starting an animated security blog to show people the ludicrousness of all this kind of stuff in plain language. I'll be Statler, and I just need someone to be Waldorf. Because this stuff really is getting Statler and Waldorf level ridiculous.
- fjsolwmv 8y agoYes, that's right, if you install software that had a bug, then if you give someone permission to modify your software, you can get a bug fixes faster.
- neilv 8y agoThere are already channels for bug fixes, and some of the friction on those channels is intentional, such as for visibility and oversight/approval.
- bilbo0s 8y agoExactly. Why even have an official channel, providing visibility and official oversight, if when it comes down to it, you're just gonna push remote code updates through the same side channel a potential hacker would use? People are saying it's for convenience. OK, but then they have to understand that doing things in that fashion is a really bad look. And now your users are set up to believe that, at least some of the updates coming from the side channel are "trust"-able.
- pedrocr 8y agoThis is a piece of code downloaded from Mozilla servers to re-enable extensions, which are other pieces of code you download from Mozilla servers. If your threat model includes not trusting Mozilla servers then you've presumably disabled browser extensions (or sideloaded them) and this issue is irrelevant to you. If you do use extensions and get updated versions from Mozilla I don't see any way in which this increases your attack surface.
- fjsolwmv 8y agoESR means extended support, not "never changes". As long as it is supported (and it is: the bug got fixed), it's appropriate for ESR.
- taxatu 8y agoCan we get a clarification: Unchecking "Allow Firefox to install and run studies" in the UI does not change "app.normandy.enabled" to "false". Then, does unchecking "Allow Firefox to install and run studies" really disable Normandy, or not?
- vesinisa 8y agoAs explained on Normandy's wiki page, they are related but two different things: > Preference rollout is meant for permanent changes that we are sure of. Shield is meant for testing variations and figuring out what, if anything, is the best thing to do. https://wiki.mozilla.org/Firefox/Normandy/PreferenceRollout#Relationship_with_Shield https://wiki.mozilla.org/Firefox/Normandy/PreferenceRollout#...
- pynabi 8y agoThat doesn't answer the question: does Normandy get disabled by the UI option or not? One can guess based on the wiki page that the answer is "no", but that's just a guess.
- robolange 8y ago"Explained" is perhaps too generous a word. I'm a software engineer and I found that page to be confusing. It seems to be written for internal Mozilla employees, not for the general public.
- stefan_ 8y agoExcept as we have learned "preference rollout" is also "installing extensions". So this is much the same as studies, but studies was disgraced, so now this is studies 2.0, no option to disable this time around. And if you look at the big normandy JSON, hey, it's all the same Pocket and heartbeat shit we've seen from studies.
- deleted 8y ago[deleted]
- SignalsFromBob 8y agoIs there a CVE for this "normandy" backdoor?
- hanif184 8y agoOkay I will try