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 ^^^