Skip to content

Commit d3cc2cd

Browse files
Richard Hainespcmoore
authored andcommitted
selinux: Update SELinux SCTP documentation
Update SELinux-sctp.rst "SCTP Peer Labeling" section to reflect how the association permission is validated. Reported-by: Dominick Grift <[email protected]> Signed-off-by: Richard Haines <[email protected]> Signed-off-by: Paul Moore <[email protected]>
1 parent 68741a8 commit d3cc2cd

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

Documentation/security/SELinux-sctp.rst

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -116,11 +116,12 @@ statement as shown in the following example::
116116
SCTP Peer Labeling
117117
===================
118118
An SCTP socket will only have one peer label assigned to it. This will be
119-
assigned during the establishment of the first association. Once the peer
120-
label has been assigned, any new associations will have the ``association``
121-
permission validated by checking the socket peer sid against the received
122-
packets peer sid to determine whether the association should be allowed or
123-
denied.
119+
assigned during the establishment of the first association. Any further
120+
associations on this socket will have their packet peer label compared to
121+
the sockets peer label, and only if they are different will the
122+
``association`` permission be validated. This is validated by checking the
123+
socket peer sid against the received packets peer sid to determine whether
124+
the association should be allowed or denied.
124125

125126
NOTES:
126127
1) If peer labeling is not enabled, then the peer context will always be

0 commit comments

Comments
 (0)