4 ms·
Besides the limitations others have mentioned users should be aware that since ydotool works by writing events directly into /dev/uinput the input will go to wh
by donio 3y ago
Besides the limitations others have mentioned users should be aware that since ydotool works by writing events directly into /dev/uinput the input will go to whatever happens to be focused at the moment. It will happily type your secrets into a chat window if you move the mouse at the wrong time.
There is no way to do the equivalent of xdotool type --window 0x600005 "my important input"
- shmerl 3y agoIt's not like xdotool is so secure in the first place. X11 is one huge hole from that perspective. Anything can read anything and all your important input can be read by some other window anyway.
- bee_rider 2y agoThis is a totally different issue; Wayland gives up the ability to provide user-aid that prevents an obvious human error. This is not really a security issue, it is a usability issue that can just happen to allow a user to make a security slip-up. In exchange, Wayland gains… well, nothing really, the idea is that it’ll protect users from malicious programs peeking at other windows on their computer. But in that case situation is already FUBAR, there’s no way to protect a computer that is already running attacks locally on itself.
- shmerl 2y agoThe idea is that to worry about security in something broken by design is a folly.
- bee_rider 2y agoRight, the idea of running hostile programs on your system is broken by design, Wayland is engaging in folly by trying to protect against it. X11 gives up that pointless quest and, by doing so, at least it can provide some extra user-assistance features (including ones that can help mitigate security related user errors).
- deleted 2y ago[deleted]
- yjftsjthsd-h 2y agoAre you posting from seL4, OpenBSD, or Genode?