Re:Firefox 115 can silently remotely disable my extension on...
by fragmede on Wednesday July 05, 2023 @01:39PM
(#36603947)
* * *
Re:Firefox 115 can silently remotely disable my extension on...
by jeroenhd on Wednesday July 05, 2023 @01:51PM
(#36604201)
They've nipped the crap inserted by adware in the bud. Sure, anyone who can pass a simple malware scan can get an addon published, but there's no doubt in my mind that getting rid of unsigned addons has helped a lot.
Re:Firefox 115 can silently remotely disable my extension on...
by BaseballPhysics on Wednesday July 05, 2023 @01:21PM
(#36603649)
> I understand this position, but I do see several trackers ("telemetry") get blocked by uBlock on my bank's website.
Which is why I'd leave uBlock whitelisted. I never said I want to block all extensions!
> I doubt Mozilla will hire someone to monitor the changes to banking URLs around the world
uBlock effectively does this for advertising domains. Why is that any different?
Re:Firefox 115 can silently remotely disable my extension on...
by jeroenhd on Wednesday July 05, 2023 @01:54PM
(#36604253)
The tricky thing is what extensions should be whitelisted and what extensions shouldn't. uBlock is easy, but what about Consent-O-Matic? What about GreaseMonkey and friends? What about Stylus? Where do you draw the line?
uBlock was just an example, of course. There are other addons that do more complex auto detection.
Re:Firefox 115 can silently remotely disable my extension on...
by drdaeman on Wednesday July 05, 2023 @02:23PM
(#36604792)
In my experience, banking websites are notoriously ass-backwards and need more hacks and patches than many other websites.
I’ve specifically used Greasemonkey to fix bank breaking pasting into fields and blocking password managers by splitting login form into deliberately broken pieces.
This type of telemetry can go die in a fire for all I'm concerned, but these trackers are particularly devious with their constantly changing domains and URLs. Addons that allow for things like regex matching are the only solution that seems to work because the Pihole blacklist doesn't seem to block them sufficiently.
Mozilla has already killed off malicious addons by enforcing their signature requirements. I'm not sure what this adds, I doubt Mozilla will hire someone to monitor the changes to banking URLs around the world (a necessity if this is indeed intended to make banking safer).