Re:Improved Process Isolation in Firefox 100
by pcwalton on Thursday May 12, 2022 @10:59PM
(#31362778)
I'm pretty sure that there's nothing preventing other apps on your desktop from listening to keystrokes that are supposed to go into Firefox, unfortunately. This is a fundamental problem with the X11 protocol and as far as I know the only real solution is to switch to Wayland.
Re:Improved Process Isolation in Firefox 100
by kramerger on Friday May 13, 2022 @02:01AM
(#31363876)
All major distros are using wayland these days.
Re:Improved Process Isolation in Firefox 100
by michaelmrose on Friday May 13, 2022 @02:45AM
(#31364170)
Along with like 1 in 5 users.
Re:Improved Process Isolation in Firefox 100
by derkades on Friday May 13, 2022 @03:18AM
(#31364376)
Ubuntu 22.04 now defaults to Wayland so that should make a big difference in the coming years
wayland has never been a pleasant experience for me, neither was pipewire. everything the nix community fawns over seems to be regressive bullshit that breaks my system. systemd is only just now becoming acceptable in that in the past year it hasn't fucked me too hard.
Re:Improved Process Isolation in Firefox 100
by hollerith on Monday May 16, 2022 @01:57PM
(#31401106)
Please stop using "nix" to mean Unix and similar systems. *nix is OK. There is an important package manager named Nix.
Re:Improved Process Isolation in Firefox 100
by michaelmrose on Friday May 13, 2022 @02:44AM
(#31364165)
None of those other apps are constantly running code written by millions of different people many of which are actively attacking you possibly right now in one tab while you are typing in the other.
It has to make a Herculean effort because it is by far the worst possible app to be typing $SensitiveMessage in.
At least Kate or gedit probably doesn't have a second tab open running a JavaScript subprocess which is presently trying to attack you so it can cryptolocker you or empty your wallet.
Re:Improved Process Isolation in Firefox 100
by ReactiveJelly on Thursday May 12, 2022 @11:15PM
(#31362882)
Yeah the keystrokes still have to go to some trusted process at the top that doesn't run untrusted code.
So it's only more secure if you think emacs / xterm / your text editor is real likely to be compromised
Chromium and dreivatives had this for years. Firefox's isolation is making progress, but it has a ways to go before it matches Chromium.
FF devs are finalizing a utility process overhaul and laying the groundwork for CFI; for years, Chromium has had both with a much more thorough implementation than FF will in the near future. However, the browser space desperately needs competition so I'll take what I can get. Sigh.
For instance, if you are typing $SensitiveMessage, you would be far better off doing that in a firefox 100 textedit box in a browser tab, rather than an xterm, or emacs, or your desktop environments preferred text editor, or anything else.
I currently use "secure keyboard" in xterm but I know that has problems.