aboutsummaryrefslogtreecommitdiffstats
path: root/security/integrity
diff options
context:
space:
mode:
authorPaul Moore <pmoore@redhat.com>2013-12-04 16:10:51 -0500
committerPaul Moore <pmoore@redhat.com>2013-12-12 17:21:31 -0500
commit446b802437f285de68ffb8d6fac3c44c3cab5b04 (patch)
tree2123c25875f8ad75114592e4755d21429765a6c0 /security/integrity
parentselinux: handle TCP SYN-ACK packets correctly in selinux_ip_output() (diff)
downloadlinux-dev-446b802437f285de68ffb8d6fac3c44c3cab5b04.tar.xz
linux-dev-446b802437f285de68ffb8d6fac3c44c3cab5b04.zip
selinux: handle TCP SYN-ACK packets correctly in selinux_ip_postroute()
In selinux_ip_postroute() we perform access checks based on the packet's security label. For locally generated traffic we get the packet's security label from the associated socket; this works in all cases except for TCP SYN-ACK packets. In the case of SYN-ACK packet's the correct security label is stored in the connection's request_sock, not the server's socket. Unfortunately, at the point in time when selinux_ip_postroute() is called we can't query the request_sock directly, we need to recreate the label using the same logic that originally labeled the associated request_sock. See the inline comments for more explanation. Reported-by: Janak Desai <Janak.Desai@gtri.gatech.edu> Tested-by: Janak Desai <Janak.Desai@gtri.gatech.edu> Cc: stable@vger.kernel.org Signed-off-by: Paul Moore <pmoore@redhat.com>
Diffstat (limited to 'security/integrity')
0 files changed, 0 insertions, 0 deletions