@micro_cat @nixCraft websites that strictly prohibit or circumvent browser functionality should be automatically flagged as untrustworthy and treated the same as a broken SSL cert.
I'm always shocked and disappointed when I hit ctrl+f only for some dumbass proprietary "find" form to pop up(looking at you github).
If anything, allowing JS to circumvent user input standards is a clear violation of the ADA since it breaks POUR standards as it breaks out of existing "normal" operations.
@nixCraft Wow, this is damning. I know Mozilla isn't focused on Linux, but this has a very simple fix.
In the meanwhile, I'm at least somewhat protected by xfce4-terminal, which warns me before pasting anything with a line break.
@adamhotep @nixCraft @FirefoxNightly @stevetex @firefox hmm... I feel like there must be more to this story than meets the eye, because I (running Firefox on X11 on Linux) tried to reproduce the issue with the proof-of-concept links provided in the message and it completely failed. My clipboard contents were not affected at all.
Not to say it shouldn't be fixed, but I am a bit skeptical about the degree of alarm that is justified here - I mean, the scope of this seems like it may be something less than the "all Firefox+X11 users" suggested by the original post.
More complicated than it looks, and apparently largely not Firefox-specific. Counterpoint in the thread from an experienced vulnerability researcher:
https://www.openwall.com/lists/oss-security/2023/10/18/5
... Though the initial researcher claims otherwise:
https://www.openwall.com/lists/oss-security/2023/10/20/7
And a partial workaround (for the terminal cases) - disabling some characters in paste:
@nixCraft requires JavaScript.
Run NoScript alongside your adblocker to prevent this and many other exploits
@nixCraft good thing I always quit Firefox as soon as Iβm done with it.
Takeaway: donβt paste from any selection while itβs running.
And maybe Bloatzilla should disable programmatic access to the PRIMARY selection, period.
Is Firefox on Wayland included in "X11" in this context? (Sometimes xorg is referred to as "X11", thus my question.)
all the cool X developers left a while ago. it's fundamentally not suited to today's requirements. but hey! the future is now!