Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
In SELinux permissive mode, the parameter with the path to the configuration file was missing. As a consequence, the sapconf script was waiting for the user input, which led to sapconf becoming unresponsive. The underlying source code has been fixed, and sapconf no longer hangs in the aforementioned situation.
Created attachment 968111[details]
sapconf-0.98-4 check_security() patch
Description of problem:
/usr/bin/sapconf waits for input (from keyboard) instead of reading from file in check_security()
Version-Release number of selected component (if applicable):
every version upto -0.98-4 (latest as of now)
How reproducible:
every time if 'SELINUX=permissive' is set in '/etc/selinux/config'
Steps to Reproduce:
1. verify 'SELINUX=permissive' is set in '/etc/selinux/config'
2. ./sapconf
Actual results:
script "locks up" waiting for keyboard input
Expected results:
script does not lock up
Additional info:
it looks like no one has tested this branch of execution. anyway, the bug and the fix are obvious, still please, see a proposed patch.
if egrep -q "^SELINUX=['\"]?permissive"; then
the bug is exactly here ^^^
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2015-1329.html
Created attachment 968111 [details] sapconf-0.98-4 check_security() patch Description of problem: /usr/bin/sapconf waits for input (from keyboard) instead of reading from file in check_security() Version-Release number of selected component (if applicable): every version upto -0.98-4 (latest as of now) How reproducible: every time if 'SELINUX=permissive' is set in '/etc/selinux/config' Steps to Reproduce: 1. verify 'SELINUX=permissive' is set in '/etc/selinux/config' 2. ./sapconf Actual results: script "locks up" waiting for keyboard input Expected results: script does not lock up Additional info: it looks like no one has tested this branch of execution. anyway, the bug and the fix are obvious, still please, see a proposed patch. if egrep -q "^SELINUX=['\"]?permissive"; then the bug is exactly here ^^^