Bug 799302 - rhui-manager running unconfined
Summary: rhui-manager running unconfined
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Update Infrastructure for Cloud Providers
Classification: Red Hat
Component: RHUA
Version: 2.0.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: John Matthews
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-02 12:48 UTC by wes hayutin
Modified: 2012-03-12 19:44 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-02 15:59:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description wes hayutin 2012-03-02 12:48:59 UTC 
Description of problem:

unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 8924 pts/2 S+   0:03 /usr/bin/python /usr/bin/rhui-manager

[root@ip-10-252-79-12 RHUIall]# rpm -qa | grep  rhui
rh-rhui-tools-2.0.59-1.el6.noarch
rh-amazon-rhui-client-2.2.38-1.el6.noarch
[root@ip-10-252-79-12 RHUIall]#
Comment 1 wes hayutin 2012-03-02 13:13:02 UTC 
rh-rhua-selinux-policy-0.0.6-1.el6.noarch
pulp-selinux-server-0.0.263-11.el6.noarch
Comment 2 Daniel Walsh 2012-03-02 15:59:57 UTC 
We don't tend to confine administrators tools, we allow them to run in the users domains.  If the application is run directly as root, we should run it as unconfined_t.  If the application is started via DBUS say via a non root user communicating with a privileged app, then we might want to confine it.

But I do not believe that is the case here.
Comment 3 James Slagle 2012-03-12 19:38:52 UTC 
Released in RHUI 2.0.2
Note You need to log in before you can comment on or make changes to this bug.