I think maybe TeamViewer actually uses the remote desktop features of display managers, probably vnc. I ran wireshark but there's a wireguard VPN session going on, so I can't know what's actually happening, and ss doesn't show the display manager listening either. Filtering by "vnc xdmcp x11" on any interfaces shows nada, but it's definitely UDP packets as I can see the IP of the other machine.
Maybe someone can correct me on this, it's probably doing something on the unix-socket level or dbus. Also, display managers aren't limited to X11, they can support Wayland sessions too. I don't think any of the display managers currently support this out of the box. If you're referring to graphical sessions, you'd have to launch each one on a different display and tty, so 4 in total.
Which can be done with a simple script, maybe something using Xvnc and a swapping of display on every line. I'm sure others might have more ideas about this than me though. Someone on reddit mentioned something interesting, instead of using local sockets, or steams pipes, or named, pipes, etc.
You can use shared memory instead. Actually you want to sandbox it and ideally not use it at all. It has the advantage of being more secure. To use it you first have to check if you have the extension in your current Xserver implementation: Code:. I've been testing this script trying to figure out how it would be used. I was assuming that USR1 is used to reset sowm but then how is sowm run in the first place?
I think it's used to start it, and not reset it. I think starting the WM using a kill signal is pretty ingenious. I use it now. The way X works has changed "recently". X used to rely on being set-uid root, and switch to a new VT. Note, even then, X might only have worked if you started it from a text VT.
In other words, I'm not sure whether this would do what you want anyway. X has now been changed so that it can use the current VT instead. Some tools such as startx have changed their behaviour, to use the new design. The design is you do not need to start any program as root in order to improve security. This works by using logind instead, a smaller background service which is started with root privileges. If you went back to running X as root, you would not need permission from logind.
I think X will probably remain compatible with this. You appear to have been trying to run X without forcing it to run as full root. In that case you need permission from logind. I worked out a trick to spoof a login. It feels like it should be possible to allocate the tty dynamically as well using openvt -s , and a script using the tty command. However, I have just frozen my screen a couple of times trying to do that AIUI the implementation of this is quite limited.
It does not provide a recovery key. I think something broke, probably logind or gdm This two lines overrides that request, and makes even possible starting all from one command, one terminal useful for init scripts or remote x starting with ssh. Here is my version of sourcejedi's answer sorry, it wouldn't go in a comment :. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.
Create a free Team What is Teams? Arguments immediately following the startx command are used to start a client in the same manner as xinit 1. The special argument '--' marks the end of client arguments and the beginning of server options. It may be convenient to specify server options with startx to change on a per-session basis the default color depth, the server's notion of the number of dots-per-inch the display device presents, or take advantage of a different server layout, as permitted by the Xorg 1 server and specified in the xorg.
Some examples of specifying server arguments follow; consult the manual page for your X server to determine which arguments are legal. All discussion of the. Keep in mind that.
0コメント