Open boosterignition opened 7 years ago
Hi @boosterignition, thanks for the report. We already have the capability to use Unix domain sockets. See here.
I think this is talking about IPC between workers? addproc
uses localhost by default (does it actually support using a unix domain socket?)
Ah, sorry. No I don't believe it supports Unix domain sockets.
Also, since this pretty much only applies to local workers, can't it just use socketpair
s? (at least on unix). For a normal socket file you have to take care of deleting it later and a linux abstract namespace unix domain socket doesn't seem to offet better permission control than a tcp socket.
There is an implementation of a unix domain socket -based cluster manager here: https://github.com/JuliaLang/julia/tree/master/examples/clustermanager/simple
This should perhaps be a package.
TCP sockets on localhost run the risk that untrusted code running on the same machine (under a different user) could connect to the system. Windows named pipes or Unix domain sockets should be used instead to avoid this vulnerability.