Unix ___domain socket: Difference between revisions

Revision as of 13:02, 11 May 2023

Revision as of 12:54, 8 January 2024

Line 1:

{{short description|Socket for exchanging data between processes executing on the same OS}}

A '''Unix ___domain socket''' aka '''UDS''' or '''IPC socket''' ([[inter-process communication]] socket) is a data [[Communicationcommunication endpoint|communications endpoint]] for exchanging data between processes executing on the same host operating system. It is also referred to by its address family <code>AF_UNIX</code>.

==Sockets==
Valid socket types in the UNIX ___domain are:<ref name="man-unix-sockets">{{cite web

| url = http://man7.org/linux/man-pages/man7/unix.7.html

| date = 30 April 2018

Line 11 ⟶ 14:

The Unix ___domain socket facility is a standard component of [[POSIX]] [[operating system]]s.

The [[API]] for Unix ___domain sockets is similar to that of an [[Internet socket]], but rather than using an underlying network protocol, all communication occurs entirely within the operating system [[Kernelkernel (operating system)|kernel]]. Unix ___domain sockets may use the file system as their address [[name space]]. (Some operating systems, like [[Linux]], offer additional namespaces.) Processes reference Unix ___domain sockets as file system [[inode]]s, so two processes can communicate by opening the same socket.

In addition to sending data, processes may send [[file descriptor]]s across a Unix ___domain socket connection using the <code>sendmsg()</code> and <code>recvmsg()</code> system calls. This allows the sending processes to grant the receiving process access to a file descriptor for which the receiving process otherwise does not have access.<ref name="neohapsis">{{cite web |url=http://archives.neohapsis.com/archives/postfix/2000-09/1476.html |date=30 September 2000 |title=Archive of the "Postfix Discussions" mailing list |access-date=29 September 2014 |archive-url=https://web.archive.org/web/20130518084034/http://archives.neohapsis.com/archives/postfix/2000-09/1476.html |archive-date=18 May 2013 |url-status=dead |df=dmy-all}}</ref><ref name="linux-cmsg-man-page">{{cite web |url=https://linux.die.net/man/3/cmsg |title=Linux man page - cmsg(3): access ancillary data |access-date=9 October 2018 |df=dmy-all}}</ref> This can be used to implement a rudimentary form of [[capability-based security]].<ref name="wheeler-secure-linux-howto">{{cite web |url=https://www.dwheeler.com/secure-programs/Secure-Programs-HOWTO/sockets.html |title="Secure Programming for Linux and Unix HOWTO", Section 3.4 "Sockets and Network Connections" |date=22 August 2004 |website=dwheeler.com |publisher=David A. Wheeler |access-date=29 September 2014}}</ref>

Line 38 ⟶ 41:

[[Category:Network socket]]

[[Category:Unix]]

{{compsci-stub}}

[[fr:Berkeley sockets#Socket unix]]