Bug 1128369 - sepolicy generate creates the corresponding shell script that requires root without a need for it
Summary: sepolicy generate creates the corresponding shell script that requires root w...
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: policycoreutils
Version: 7.2
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Vit Mojzis
QA Contact: Dalibor Pospíšil
Depends On:
TreeView+ depends on / blocked
Reported: 2014-08-09 15:31 UTC by (GalaxyMaster)
Modified: 2019-02-27 13:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-02-27 13:53:13 UTC

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
CentOS 7484 None None None Never

Description (GalaxyMaster) 2014-08-09 15:31:24 UTC
Description of problem:

When you run "sepolicy generate" it generates files to define a policy. It also creates <policy_name>.sh file that is supposed to help the user to package the policy module into an RPM package. Unfortunately, in the current state the created script tries to do 2 things at once:

1. install the generated policy into the system
2. package the policy into an RPM package.

While item 1 requires root powers (or more explicitly, administrative rights) to modify the system, item 2 does not require such powers.

It would be nice if the installation and update parts were separated logically inside the created shell script: e.g. if the script is launched with "install" or "update" arguments it will demand root, but if it's executed with "package" - it will simply package the created policy module into an RPM package.

Additional info:

It was also spotted that the auto-generated manual page for the policy module contains a couple of typos:

"other roles need to be transition into" => s/transition/transitioned/
"When using a a non login role," => s/a a non/a non/

Also, the generated manual page contain excessive list of SELinux booleans that are not specifically related to the generated policy module, but to the whole SELinux policy itself. This is redundant and is better to be excluded from a policy module man page (we still have the SEE ALSO list at the end of the page :).

Comment 4 Zdenek Pytela 2019-02-27 13:53:13 UTC
This issue was not selected to be included in Red Hat Enterprise Linux 7.7 because it is seen either as low or moderate impact to a small number of use-cases. The next release will be in Maintenance Support 1 Phase, which means that qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available.

We will now close this issue, but if you believe that it qualifies for the Maintenance Support 1 Phase, please re-open; otherwise, we recommend moving the request to Red Hat Enterprise Linux 8 if applicable.

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