Bug 254881 - Multiple contexts on directories / sub-dir
Multiple contexts on directories / sub-dir
Product: Fedora
Classification: Fedora
Component: seedit (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Yuichi Nakamura
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-08-26 07:20 EDT by Patrick Proy
Modified: 2008-05-06 15:44 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 15:44:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Patrick Proy 2007-08-26 07:20:27 EDT
Description of problem:
When I try to set different permissions on a directory based on the inclusion of
sub-dir or not. Only one file context is created.

For ex (the two lines where in different policies but in this order in all.sp): 
allow /var/mailscan/* w,s,r;
allow /var/mailscan/** s,r;

a context is only created for /var/mailscan/* ,resulting in : 
  /var/mailscan(|/[^/]*) system_u:[...]
and applied. 

So the permissions "allow /var/mailscan/** s,r;" is not set.

Maybe it is a selinux limitation. If not, two contexts should be created.

Version-Release number of selected component (if applicable):


How reproducible:

Try a similar config.

Steps to Reproduce:
Actual results:

/var/mailscan subdirs not searchable

Expected results:

/var/mailscan subdirs searchable.

Additional info:
Comment 1 Yuichi Nakamura 2007-09-03 21:05:56 EDT
It seems correct behavior.
When subdirs exists already, 
like following is generated.
  /var/mailscan/subdir/(/.*) system_u:[...]

However, subdirs does not exists, and it is created after configuring poilcy,
such entries are not generated and it does not work.
This will be resolved next version (2.2.0), but it is still under development, 
only exists in svn tree.
Comment 2 Bug Zapper 2008-04-04 03:32:16 EDT
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
Comment 3 Bug Zapper 2008-05-06 15:44:38 EDT
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.