mirror of
https://github.com/openvswitch/ovs
synced 2025-08-22 09:58:01 +00:00
922247c684
Currently in the case of command line arguments punix/unix, on Windows we create a file, write a TCP port number to connect. This is a security concern. This patch adds support for the command line arguments punix/unix trying to mimic AF_UNIX behind a local named pipe. This patch drops the TCP socket implementation behind command line arguments punix/unix and switches to the local named pipe implementation. Since we do not write anything to the file created by the punix/unix arguments, switch tests to plain file existence. Man pages and code comments have been updated. Signed-off-by: Alin Gabriel Serdean <aserdean@cloudbasesolutions.com> Acked-by: Paul Boca <pboca@cloudbasesolutions.com> Signed-off-by: Gurucharan Shetty <guru@ovn.org>
18 lines
847 B
Groff
18 lines
847 B
Groff
.IP "\fB\-\-unixctl=\fIsocket\fR"
|
|
Sets the name of the control socket on which \fB\*(PN\fR listens for
|
|
runtime management commands (see \fBRUNTIME MANAGEMENT COMMANDS\fR,
|
|
below). If \fIsocket\fR does not begin with \fB/\fR, it is
|
|
interpreted as relative to \fB@RUNDIR@\fR. If \fB\-\-unixctl\fR is
|
|
not used at all, the default socket is
|
|
\fB@RUNDIR@/\*(PN.\fIpid\fB.ctl\fR, where \fIpid\fR is \fB\*(PN\fR's
|
|
process ID.
|
|
.IP
|
|
On Windows a local named pipe is used to listen for runtime management
|
|
commands. A file is created in the absolute path as pointed by
|
|
\fIsocket\fR or if \fB\-\-unixctl\fR is not used at all, a file is
|
|
created as \fB\*(PN.ctl\fR in the configured \fIOVS_RUNDIR\fR
|
|
directory. The file exists just to mimic the behavior of a Unix domain socket.
|
|
.IP
|
|
Specifying \fBnone\fR for \fIsocket\fR disables the control socket
|
|
feature.
|