mirror of https://github.com/mkerrisk/man-pages
unix.7: Enhance statement about changing sockets ownership and permissions
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
b1ef409dc7
commit
ce552c68fb
|
@ -503,7 +503,6 @@ but the implementation details differ.)
|
|||
.SH NOTES
|
||||
In the Linux implementation, sockets which are visible in the
|
||||
filesystem honor the permissions of the directory they are in.
|
||||
Their owner, group, and permissions can be changed.
|
||||
Creation of a new socket will fail if the process does not have write and
|
||||
search (execute) permission on the directory the socket is created in.
|
||||
|
||||
|
@ -513,6 +512,12 @@ which ignore permissions for UNIX domain sockets.
|
|||
Portable programs should not rely on
|
||||
this feature for security.
|
||||
|
||||
A socket's owner, group, and permissions can be changed (using
|
||||
.BR chown (2)
|
||||
and
|
||||
.BR chmod (2)).
|
||||
.\" However, fchown() and fchmod() do not seem to have an effect
|
||||
|
||||
Binding to a socket with a filename creates a socket
|
||||
in the filesystem that must be deleted by the caller when it is no
|
||||
longer needed (using
|
||||
|
|
Loading…
Reference in New Issue