wayland-keylogger VS qubes-issues

Intercepting inputs meant for other apps is easy and it's already been done via LD_PRELOAD.

And all of this just for supposedly better "security", that can easily circumvented with trivial attacks.

Not in the same sense that there's a keylogger included with Windows, no. It's that it's easier to do on Xorg as opposed to Wayland. This isn't to say that it's impossible, however.

You can have keylogger on Wayland also without root priviledge. It's trivial: https://github.com/Aishou/wayland-keylogger

> you can still deliver different experiences at runtime — but you’re not likely to have the superuser privileges needed to run a leylogger or read ~/.ssh/id_rsa, etc, at that point.

Keyloggers are trivial to do in userspace Linux via LD_PRELOAD attacks[0], and typically your user account has permission to read ~/.ssh/id_rsa.

[0] https://github.com/Aishou/wayland-keylogger

I have read that bare Linux is totally insecure (https://github.com/Aishou/wayland-keylogger) unless you use some means of sandboxing. That's why I have been reading a lot about firejail, AppArmor, Tomoyo, etc.

Are you using an Nvidia GPU?

https://github.com/QubesOS/qubes-issues/issues/5104

https://github.com/QubesOS/qubes-issues/issues/7591

If not, try this: https://github.com/QubesOS/qubes-issues/issues/6880#issuecom...

There is no tearing on my Librem laptops.

> The gnome desktop will be important for adoption

Gnome is too opinionated to adjust it for Qubes: https://github.com/QubesOS/qubes-issues/issues/1806#issuecom...

However you can easily install KDE.

Are we still getting a second RC for 4.2? I remember originally we were told that we would because of the new Qubes builder tool, but I see the milestone jumped to 96% since last I checked, are we getting a full release at the 100% github milestone? Or what happens when it hits 100? https://github.com/QubesOS/qubes-issues/milestone/26

This project was never stagnant, a lot of things are always happening here: https://github.com/QubesOS/qubes-issues.

Concerning the certified hardware, few vendors try to make the certification, and also coreboot is required: https://www.qubes-os.org/doc/certified-hardware/#hardware-ce...

Not precisely, but a lot is going on in this direction: https://github.com/QubesOS/qubes-issues/issues/1939.

I read that there is a plan to implement per-VM encryption (https://github.com/QubesOS/qubes-issues/issues/1293)

Looks like a fix might be close at hand: This pull request is linked to the issue "Hardware support: Ryzen 7000 series / Zen 4 / AM5."

This bug report indicates that "kernel-latest" will be in the next official build of the Qubes 4.1 install ISO. Thing is on the mirrors the last release of 4.1 (actually 4.1.1) was July 18th 2022, and thus the title of this post.