From cd54ca5066e9fa8ee62f32eac7352c5e08d47c28 Mon Sep 17 00:00:00 2001
From: Garrett D'Amore 0644.
| + + | ++Not all systems validate these permissions. +In particular, illumos and Solaris are known to ignore these permission +settings when connecting. + | +
| + + | ++The best practice for limiting access is to place the socket in a +directory writable only by the server, and only readable and searchable +by clients. +All mainstream POSIX systems will fail to permit a client to connect +to a socket located in a diretor for which the client lacks search (execute) +permission. + | +
| + + | +
+Also consider using the NNG_OPT_IPC_PEER_UID property from within a
+a pipe notification callback (nng_pipe_notify())
+to validate peer credentials.
+ |
+
NNG_OPT_IPC_SECURITY_DESCRIPTORLimit the number of iterations when looping to COUNT iterations. +For protocols that only send, this will only send COUNT messages before +exiting. +For protocols that only receive, this will only receive COUNT messages +before exiting. +For protocols that involve a full exchange, this will only perform COUNT +exchanges (each exchange is characterized by at most a single send, and +one or more receives.) +If COUNT is zero, then an infinite number of iterations is performed.
+Give up receiving messages after SEC seconds pass without any received messages.
+Set the maximum message size socket will accept to COUNT bytes. +Messages larger than this will be discarded. +The default is 1048576 (1 MB). +To eliminate any restriction, use 0.
+