From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12 Description of problem: When using the GUI SELinux Administration toole (system-config-selinux) to add File Labeling objects you are unable to enter in (/.*)? at the end of a file path. The error you get is: sh: -c: line 0: syntax error near unexpected token `(' sh: -c: `{ semanage fcontext -a -t mysqld_db_t -r so -f 'all files' /home/database/mysql(/.*)?; } 2>&1' If you run semanage manually on the command line adding single quotes to the file path, the command works properly and the context is added, example: [root@server ~]# semanage fcontext -a -t mysqld_db_t -r so -f 'all files' '/home/database/mysql(/.*)?' [root@server ~]# Version-Release number of selected component (if applicable): policycoreutils-gui-1.33.12012.el5 How reproducible: Always Steps to Reproduce: 1. Load SELinux Administration 2. Try to add a new file context to File Labeling that contains (/.*)? at the end 3. What the error window pop up (system-config-selinx must be launched from the command line to easily see the error listed in the terminal as the gui pop-up windows just has a red stop sign and OK button) Actual Results: The context was not added, and I received an error. Expected Results: the context should have been added Additional info: Looks like the context string just needs to be placed in single quotes before being sent to the command line.
Fixed in policycoreutils-1.33.12-15.el5.src.rpm Possible release via zstream?
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Fixed in policycoreutils-1.33.12-14.1.el5
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0206.html