An exposed endpoint allowing "anyone" to connect to the system compositor is a bad idea wherever it.
It has been the plan for the system compositor not to create an endpoint on the filesystem and instead to pass a connection FD to the session compositors and clients. (Although we could specify a file to create on the command-line for debugging purposes.) I think Robert Ansell started work on the system compositor code to pass the FD via dbus. Surely not creating the FD at all is a better fix than just moving the fallback location? (/tmp is only used if =$XDG_RUNTIME_DIR is not set) Notes: A suitable FD can be created using connector->client_socket_fd() - there's been an an example in <mir>/examples/basic_server_configuration.cpp for over a year. We are also using this approach with "trust sessions" (to allocate sockets before launching new participants in the trust session). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322300 Title: [enhancement] Please move /tmp/mir_socket to /run/mir_socket (or similar) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1322300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
