Re: emacsclient socket ownership

[Stefan Monnier <monnier@iro.umontreal.ca>]

> There is no /run on macOS, and I'm pretty sure at least OpenBSD have
> rejected the idea.

It's OK: we can use OS-specific filenames.

And we'd want to preserve compatibility between old emacsclient and new
server.el and vice versa.

> Would not a better choice be to locate the socket at
> ${HOME}/.emacs.d/${something} instead?

That's another option, indeed.
IIRC it tends to work poorly when $HOME is on a network file system.

> At heart, I don't think this is really a security issue, so much as that
> root is the ultimate force for bypassing all protection in the Unix world.
> Without going to something akin to SELinux, or some similar MAC
> system,  there isn't any way to prevent root accessing any socket, by
> design.

The problem is not Emacs trying to prevent root's emacsclient from
connecting, but root's emacsclient trying to avoid connecting
inadvertently to an attacker's socket.


        Stefan