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.
Bug 854615 - AVCs when running bcfg2 test with disabled unconfined and unlabelednet
Summary: AVCs when running bcfg2 test with disabled unconfined and unlabelednet
Keywords:
Status: CLOSED DUPLICATE of bug 807678
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: selinux-policy
Version: 6.4
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Miroslav Grepl
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-05 12:49 UTC by Michal Trunecka
Modified: 2014-09-30 23:33 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-06 05:02:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Michal Trunecka 2012-09-05 12:49:08 UTC 
Description of problem:
When unconfined and unlabelednet modules are disabled, running automated test of bcfg2 FAILed and causes following AVC:

----
time->Wed Sep  5 14:37:39 2012
type=SYSCALL msg=audit(1346848659.240:29918): arch=c000003e syscall=49 success=yes exit=0 a0=6 a1=7fff5414b020 a2=10 a3=ff00 items=0 ppid=1 pid=30341 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=6 comm="bcfg2-server" exe="/usr/bin/python" subj=unconfined_u:system_r:initrc_t:s0 key=(null)
type=AVC msg=audit(1346848659.240:29918): avc:  denied  { name_bind } for  pid=30341 comm="bcfg2-server" src=6789 scontext=unconfined_u:system_r:initrc_t:s0 tcontext=system_u:object_r:cyphesis_port_t:s0 tclass=tcp_socket

In addition, in permissive mode, the test PASSes with only this AVC. The test PASSed with no AVCs with both mentioned modules enabled.


Version-Release number of selected component (if applicable):
selinux-policy-3.7.19-155.el6_3.noarch
selinux-policy-targeted-3.7.19-155.el6_3.noarch
bcfg2-1.2.1-1.el6.noarch
bcfg2-doc-1.2.1-1.el6.noarch
bcfg2-web-1.2.1-1.el6.noarch
bcfg2-server-1.2.1-1.el6.noarch


How reproducible:
always

Steps to Reproduce:
1. semodule -d unconfined; semodule -d unlabelednet
2. Run following automated test 
  /CoreOS/selinux-policy/Regression/bz805742-SELINUX-ERR-when-using-config-tools-to-install


Actual results:
Test FAILed and AVC showed up

Expected results:
Test PASSes with no AVC
Comment 2 Miroslav Grepl 2012-09-06 05:02:48 UTC 
This will be fixed by new policy for this service.

*** This bug has been marked as a duplicate of bug 807678 ***
Comment 3 Miroslav Grepl 2012-09-06 05:04:23 UTC 
Did it happen by default or did you setup this port?
Comment 4 Michal Trunecka 2012-09-06 06:47:21 UTC 
Port 6789 is commonly used for bcfg2, it is also mentioned in official documentation, e.g. here http://docs.bcfg2.org/appendix/guides/authentication.html    But there is no default port, you have to choose some by yourself using bcfg2 interactive initialization script.
Comment 5 Miroslav Grepl 2012-09-06 12:49:55 UTC 
Ok. Thx.
Note You need to log in before you can comment on or make changes to this bug.