28 ms·
> Are there plans to move to Wayland? As far as I know, the difficulty on OpenBSD would be input. The Wayland world relies on evdev, so they either have to pat
by floatboth 6y ago
> Are there plans to move to Wayland?
As far as I know, the difficulty on OpenBSD would be input. The Wayland world relies on evdev, so they either have to patch it to use their interfaces, or implement evdev.
On FreeBSD, we have a lot of devices supporting evdev :) Including the next generation HID stack: https://github.com/wulf7/iichid https://github.com/wulf7/iichid (currently external, but would be merged into the system eventually)
Also there's device discovery, for which we use https://github.com/FreeBSDDesktop/libudev-devd https://github.com/FreeBSDDesktop/libudev-devd to pretend to be udev, but I suspect the OpenBSD people might not like solutions like that :D (Actually, does OpenBSD even have anything devd-like that provides hotplug notifications?)
- genr8 6y agoVery helpful thank you. I believe you are correct on all fronts. Does anyone know if "their interfaces" prevent the Xorg/Xinput keylogger "bug" as is, even without EVdev or Udev? The man page seems like it does use Xinput, but it also mentions Xwayland https://man.openbsd.org/xinput.1 https://man.openbsd.org/xinput.1 So I think that if Wayland does work, that interface would take care of the issue. I am in the middle of something else or I would try and figure it out myself, but it would take a long time.
- floatboth 6y agoNo, the "xorg keylogger" issue has nothing to do with the low level stuff (evdev is how the windowing system gets info from the kernel, udev is how the windowing system enumerates devices and gets hotplug notifications). The "xorg keylogger" issue is a fundamental property of the X11 protocol, it's between the server and clients — all clients get enormous amounts of access to all kinds of global state over the X11 socket.