Currently in case of private-tmp option we mount an empty /tmp with whitelisted /tmp/.X11-unix. Additionally we may expose it as read-only. The read-only mount flag does not prevent using connect() syscall on the socket.
@Vincent43 Is the easiest way to do this to build it in to --private-tmp or to just add it to the profiles directly?
I think it should be built into --private-tmp directly to avoid cluttering profiles.
Going to close this as this should now be implemented.
Most helpful comment
I think it should be built into
--private-tmpdirectly to avoid cluttering profiles.