this post was submitted on 29 Apr 2024
473 points (96.1% liked)
linuxmemes
20463 readers
140 users here now
I use Arch btw
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules
- Follow the site-wide rules and code of conduct
- Be civil
- Post Linux-related content
- No recent reposts
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
When running Wayland, one X server is started per X application. So that application won't be able to e.g. keylog others.
I personally don't care about security here, it's all about a flicker free Multi-monitor experience with different refresh rates per monitor. X just can't do that under any circumstances.
I run X in a multi monitor setup with different refreshrates AND resolutions and it is flicker free, I think that honestly is something that comes down more to your window manager or even your graphics rather than just X itself.
That particular vulnerability is one of the 6% that Wayland doesn't have.
I mean I'd be happy to hear the other vulnerabilities then, cause I find it fairly unbelievable you can know how they're handled on every single Wayland compositor
You're missing the point. When you run an x client in wayland, you are still running an x server. Every vulnerability an x server has, xwayland has. I don't need to name anything specific because you can legitimately go and look this up yourself.
Don't think you are fully safe from keylogging in xwayland either, you are only safe from keylogging in wayland apps, xwayland clients can keylog other xwayland clients because x servers can see other x servers, in other words, they are all still very much running seperate PIDs on your system which means at the very least they can still touch each other. XWayland, by default, does not really sandbox clients because why exactly would it need to? Do you realize exactly how much of a feat that would take to truly isolate an x server from the rest of your system? That is an inherent flaw with X itself because X never set out to acheive those goals in the first place.
If you are at the point where you have to be worried about protecting your xsession or wayland session, you need to make a fresh install and tighten your security accordingly. All that tightening down your window manager does is make an attacker go for a lower hanging fruit on your system, that's why you should make your machine unfeasible to even attack in the first place. You can go run around and try to tighten every little nook and cranny, but if someone is determined to get into your system, they will eventually get in. The malicious parties we are trying to defend against with general security practices are not nation state hackers, they are skids and standard malware.
Do you have separate scaling factors on the two monitors? I need 100% scaling on one and 175% scaling on the other, which I've not been able to figure out under x11
Yes, one is scaled 2x, I have a 4k60 and a FHD165. I'd recommend doing this with your autostart script using xrandr
Ah, right. That's fine with integer scaling, but if you try to use fractional scaling with xrandr, it gets all blurry. I'll consider 2x scaling though
1.5 scaling works too, I've done it with my laptop with qhd and fhd