On Tue, Mar 16, 2010 at 10:54 AM, Matthias Clasen <mclasen@xxxxxxxxxx> wrote: > > Any reason this cannot be an abstract socket ? Of course, then you have > to check peer creds and figure out a way to communicate the socket name, > but at least you don't have to worry about the usual races and > permission problem you have with unix sockets. People - reliably finding other programs and initiating communication with them is 99% of the reason that DBus was created and exists in the OS. In this case, the right thing is to claim a bus name (org.blah.MyApp), export a method on it "org.blah.MyApp.GetSocket", which returns the randomly-named path to your socket in /tmp. Using abstract sockets does NOT mean you don't have to worry about permissions. Any other uid can still connect to the socket, so you either need to do some sort of peer credentials if you want to restrict it to the same uid. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
