3 ms·
Which is a good thing. It lets you do automation on GUI tools that otherwise don't support automation (xdotool). It's something I hope Wayland and MIR will supp
by panzi 12y ago
Which is a good thing. It lets you do automation on GUI tools that otherwise don't support automation (xdotool). It's something I hope Wayland and MIR will support. Of course there should probably be some kind of permissions system. E.g. you need to start a process in a special way so it can do these things or there is some kind of white list of programs that are allowed to do this.
Oh and another application: Mapping a gamepad to keyboard and mouse for games that don't otherwise support gamepads. (See http://qjoypad.sourceforge.net/ http://qjoypad.sourceforge.net/ and my fork with additional features https://github.com/panzi/qjoypad https://github.com/panzi/qjoypad)
- krschultz 12y agoYou have to admit that it is a big security problem.
- panzi 12y agoHow? A program that runs on your computer has access to all your files anyway. How is it anymore of a security problem if it can't just access your files, change configurations, run other programs but can also send X11 events to other programs? If I can't use something like QJoyPad under Wayland/MIR I won't use Wayland/MIR.
- pmahoney 12y ago> A program that runs on your computer has access to all your files anyway. This is also a security problem. If I have the means to run a program (downloaded from the internet; don't fully trust) in a sandbox that restricts its filesystem access, it'd be nice to also not allow it to control my whole GUI session.
- panzi 12y agoWell, yeah. A sandbox should be able to control restrict, but in principle I want to have the ability to control other windows.