aboutsummaryrefslogtreecommitdiffstats
path: root/man7/unix.7
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2016-06-17 18:40:10 +0200
committerMichael Kerrisk <mtk.manpages@gmail.com>2016-06-20 14:00:37 +0200
commitce552c68fb0a0920656d77dcfb0ddb8a9ff7a681 (patch)
treefa748a55511f6495563276ee2307e86e1ebf5e03 /man7/unix.7
parentb1ef409dc7dd412e459bc120ddd31faf5ce374da (diff)
downloadman-pages-ce552c68fb0a0920656d77dcfb0ddb8a9ff7a681.tar.gz
unix.7: Enhance statement about changing sockets ownership and permissions
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Diffstat (limited to 'man7/unix.7')
-rw-r--r--man7/unix.77
1 files changed, 6 insertions, 1 deletions
diff --git a/man7/unix.7 b/man7/unix.7
index 618422df9a..804ed20cfb 100644
--- a/man7/unix.7
+++ b/man7/unix.7
@@ -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