Re: Wayland Is Coming

On Mon, 13 May 2024 09:49:34 -0000 (UTC)
Lawrence D'Oliveiro <ldo@nz.invalid> wrote:

On Mon, 13 May 2024 08:00:33 -0000 (UTC), Muttley wrote:
>

On Sun, 12 May 2024 20:37:18 -0000 (UTC)
Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
>

On Sun, 12 May 2024 08:44:04 -0000 (UTC), Muttley wrote:
>

And how do you propose to restrict access to specific processes?
Process name, user, some kind of certificate? All these things can be
spoofed.

>
Process identity can’t be spoofed.

 
Really? So what sort of idenfication system prevents spoofing then?

>
The kernel. It’s a feature of Unix sockets, because of the fact that
they’re strictly local.

FFS man, you know perfectly well I'm talking about remote processes on
another machine.

A side plug in that seems to have to run as a server alongside the
wayland server. Very efficient I'm sure.

>
It’s called “modularity”.

Graphics networking should be built in for speed.

Wayland is only reachable via a Unix socket, which, unlike TCP/IP ports,
is subject to standard Linux filesystem protections.

Yes, we know that already.

Waypipe extends to relaying that via a Unix socket on the remote machine,
which is subject to standard Linux filesystem protections there.

Wtf are you babbling about? Unix sockets can't connect over TCP and once
you're on another machine spoofing is technically simple.

You see how all the parts fit together, without compromising security?

I don't think you understand basic networking.

X can also use unix swockets

>
No it can’t. An X display has to be a number, not a name.

*sigh*

I don't think you understand X11 either.

https://unix.stackexchange.com/questions/196677/what-is-tmp-x11-unix

"The X server has several ways of communicating with X clients (apps). The
most common one to use, at least on the same machine, is a Unix-domain socket."

"The X server puts its socket in /tmp/.X11-unix:"