Bug 596415 - bug in git policy
bug in git policy
Product: Fedora
Classification: Fedora
Component: selinux-policy (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Fedora Extras Quality Assurance
: 596411 596412 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2010-05-26 13:58 EDT by Dominick Grift
Modified: 2010-06-08 15:27 EDT (History)
2 users (show)

See Also:
Fixed In Version: selinux-policy-3.7.19-23.fc13
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-05-29 09:10:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
patch to remove buggy rules in git policy module (1.45 KB, patch)
2010-05-26 13:58 EDT, Dominick Grift
no flags Details | Diff

  None (edit)
Description Dominick Grift 2010-05-26 13:58:09 EDT
Created attachment 416954 [details]
patch to remove buggy rules in git policy module

Description of problem:

There is a bug in git policy that allows users to circumvent the restrictions in place for users executing content.

By removing these buggy rules git session content will be equal to userdom_user_home_content and same rules will apply

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

See attached patch:
Comment 1 Daniel Walsh 2010-05-26 16:44:09 EDT
Fixed in selinux-policy-3.7.19-22.fc13.noarch
Comment 2 Miroslav Grepl 2010-05-27 03:31:48 EDT
*** Bug 596411 has been marked as a duplicate of this bug. ***
Comment 3 Miroslav Grepl 2010-05-27 03:32:10 EDT
*** Bug 596412 has been marked as a duplicate of this bug. ***
Comment 4 Fedora Update System 2010-05-28 08:27:22 EDT
selinux-policy-3.7.19-22.fc13 has been submitted as an update for Fedora 13.
Comment 5 Dominick Grift 2010-05-29 09:10:15 EDT
Confirmed to be fixed
Comment 6 Fedora Update System 2010-06-08 15:25:52 EDT
selinux-policy-3.7.19-23.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

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