On Fri, May 23, 2014 at 08:26:31AM -0700, Ben Pfaff wrote:
> On Fri, May 23, 2014 at 11:54:11AM +0900, YAMAMOTO Takashi wrote:
> > > According to _Unix Network Programming_, only the umask controls the
> > > permissions of a Unix domain socket created by bind(). This makes it
> > > difficult to co
On Fri, May 23, 2014 at 11:54:11AM +0900, YAMAMOTO Takashi wrote:
> > According to _Unix Network Programming_, only the umask controls the
> > permissions of a Unix domain socket created by bind(). This makes it
> > difficult to correctly control permissions on sockets in a
> > multithreaded proce
> According to _Unix Network Programming_, only the umask controls the
> permissions of a Unix domain socket created by bind(). This makes it
> difficult to correctly control permissions on sockets in a
> multithreaded process, since the umask is not thread-specific.
> Therefore, currently bind_un
According to _Unix Network Programming_, only the umask controls the
permissions of a Unix domain socket created by bind(). This makes it
difficult to correctly control permissions on sockets in a
multithreaded process, since the umask is not thread-specific.
Therefore, currently bind_unix_socket(
