Since Wayland has been added to the criteria for recommended Linux distros and to the Linux overview in the Knowledge Base, shouldn’t Privacy Guides recommend setting up Brave to use Wayland as well in the configuration section? Installed it yesterday and it uses XWayland by default (tested with the xwininfo command). I’m not sure if this would negatively impact the fingerprint, but it’s possible to achieve that by setting the #ozone-platform-hint flag to Auto on brave://flags, or by adding the --enable-features=UseOzonePlatform --ozone-platform=wayland settings to the command/desktop entry.
1 Like
u can also just install it as a flatpak to make it use wayland by default
From Privacy Guides browsers page:
We advise against using the Flatpak version of Brave, as it replaces Chromium’s sandbox with Flatpak’s, which is less effective. Additionally, the package is not maintained by Brave Software, Inc.
1 Like
Yeah. I need update on this
1 Like
My understanding is that xwayland is just fine with regards to security. The security benefits of wayland are present regardless of whether the app is native or run via xwayland. The important part is the operating system using wayland instead of x11.
My understanding is the benefits of native wayland applications are mostly cosmetic. Better font scaling to be specific.
But I’m no expert.
From what I understand, windows in XWayland are all still bound together under the same X11 process and can look at each other’s contents and inputs. According to the Arch Wiki:
Security: XWayland is an X server, so it does not have the security features of Wayland
1 Like
Ah, thank for sharing that. I guess it makes sense that the compatibility layer is singular and not sandboxed. Either for resource usage reasons or for simplicity of development.
In that case, as long as the native Wayland version of Brave is reliable, it does seem like a good idea to recommend enabling it. The fact that Brave themselves haven’t enabled it suggest that either they aren’t ready to support it, or it has some flaw(s) compared to the X11 version.
I have been using it every once in a while for the past couple weeks, although my main browser is still Firefox, so there might be issues I didn’t run into — stuff like hardware acceleration and such. I didn’t find any explanation from Brave as to why they haven’t enabled the Auto flag by default, but right now it seems like the best option, in my opinion
1 Like