wayland-keylogger VS developer-center

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.

If you have any questions or suggestions about the system, please feel free to join the discussion on the Deepin forum: **https://bbs.deepin.org. Meanwhile, if you find any bugs while using the system, please don't hesitate to report them to us by opening an issue at https://github.com/linuxdeepin/developer-center/issues. Thank you for your support!

Sorry, https://github.com/linuxdeepin/developer-center/issues/2755

https://github.com/linuxdeepin/developer-center/issues/2819 usually less extreme, but it's an outcome of how X11 is designed

Welcome to discuss the features you want in the starting stage of this project at https://github.com/linuxdeepin/developer-center/discussions/3236.

Abort the installation. Try again, you may also try to flash the USB stick again. If this won't work, report issue here https://github.com/linuxdeepin/developer-center/issues

Done - https://github.com/linuxdeepin/developer-center/issues/3010

Create issue here and say what you did so far. https://github.com/linuxdeepin/developer-center/issues It look like it may be a mesa bug, but let's ask deepin devs first

I already reported this issue here https://github.com/linuxdeepin/developer-center/issues/2138. It's probably a problem for everyone. I guess It'll be fixed in December in next release https://www.deepin.org/en/developer-community/planning/

Im not sure there is anything you can do. Deepin is currently using ver. 460 driver which is relatively outdated and probably doesn't even introduce support for 3060. I'd look up if that's really the case and if yes let devs know of this issue https://github.com/linuxdeepin/developer-center/issues