Security Enhanced Linux
What's New
Frequently Asked Questions
Background
Documents
License
Download
Participating
Mail List
Archives
Remaining Work
Contributors
Related Work
Press Releases
Information Assurance Research
NIARL In-house Research Areas
Mathematical Sciences Program
Sabbaticals
Computer & Information Sciences Research
Technology Transfer
Advanced Computing
Advanced Mathematics
Communications & Networking
Information Processing
Microelectronics
Other Technologies
Technology Fact Sheets
Publications
Related Links
|
SELinux Mailing ListRe: Socket and inode label consistency
From: Casey Schaufler <casey_at_schaufler-ca.com>
Date: Wed, 27 Aug 2008 15:53:19 -0700
Would I be going too far out on a limb to suggest you change the code so that it changes both? I know that SELinux would require work to figure out what context to put on the sock based on the context of the task, socket inode, sock, port and address family, still that shouldn't be an insurmountable obstacle. Especially if you limit changes to the MLS portion of the label. Paul points out some edge case conditions for TCP that might make really supporting that protocol iffy. True enough. I wouldn't see changing labels on a TCP connection showing up in any but very low level system sort of uses where you need to be extraordinarily careful in any case. I don't see those dangers as a real stopper.
> The former is used to authorize access to the socket api. The latter -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with the words "unsubscribe selinux" without quotes as the message.Received on Wed 27 Aug 2008 - 18:53:28 EDT |
|
Date Posted: Jan 15, 2009 | Last Modified: Jan 15, 2009 | Last Reviewed: Jan 15, 2009 |