Description of problem:<br />
sealert outputs sh errors when an alert description contains parenthesis. Example text that causes error:<br />
SELinux is preventing /usr/sbin/httpd from execute access on the file /var/tmp/ffiasFfSA (deleted).<br />
<br />
The console output that occurs when this bug is triggered is:<br />
sh: -c: line 0: syntax error near unexpected token `('<br />
sh: -c: line 0: `{ rpm -qf /var/tmp/ffiasFfSA (deleted); } 2>&1'<br />
<br />
Version-Release number of selected component (if applicable):<br />
setroubleshoot-server-3.0.47-3.el6_3.x86_64 : SELinux troubleshoot server<br />
<br />
How reproducible:<br />
Attempt to parse effected audit log.<br />
<br />
Steps to Reproduce:<br />
1. Normal execution of the program (sealert -a /var/log/audit/audit.log<br />
<br />
Actual results:<br />
Spurious STDERR output<br />
<br />
Expected results:<br />
Normal output only<br />
<br />
<br />
Additional info:<br />
It seems that the end result is acceptable, as sealert displays information about the alert and suggested actions to resolve. The STDERR output doesn't -seem- to cause problems.<br />
<br />
Attached is a log containing data triggering this bug.<br />
<br />
I have also reported this upstream as it should effect them as well:<br />
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=851824">https://bugzilla.redhat.com/show_bug.cgi?id=851824</a> [<a href="https://bugzilla.redhat.com/show_bug.cgi?id=851824" target="_blank">^</a>]
↧