Research
Skip Research Menus
Research MenuSecurity 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: pipefs issue
From: Stephen Smalley <sds_at_tycho.nsa.gov>
Date: Thu, 31 May 2007 10:25:45 -0400
That is just a pipe between the parent and child, likely to feed input to the child and/or to collect the output of the child.
> Is this configurable so that I can prevent the pipefs from being I assume you are using some interface to spawn the child, and that interface includes the creation of a pipe for the parent-child communication. Are you sure you don't need that communication to provide input to the child or to collect the output of it? If so, then use a different interface, or dontaudit the denial. -- Stephen Smalley National Security Agency -- 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 Thu 31 May 2007 - 10:25:48 EDT |
|
Date Posted: Jan 15, 2009 | Last Modified: Jan 15, 2009 | Last Reviewed: Jan 15, 2009 |