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 834413 - RFE: cman without root-group privileges
Summary: RFE: cman without root-group privileges
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: cluster
Version: 6.4
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: rc
: 6.4
Assignee: Fabio Massimo Di Nitto
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks: 733221
TreeView+ depends on / blocked
 
Reported: 2012-06-21 19:19 UTC by mick
Modified: 2012-07-03 08:37 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-02 07:12:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description mick 2012-06-21 19:19:12 UTC
Request for Enhancement


summary
---------
MRG Messaging needs the ability for our clustered brokers to
get quorum changes in CPG order, but without the necessity for
our qpidd executable to run with root, or root-group privileges.



explanation
---------------
Many customers and potential customers of the MRG Messaging
system request our clustering feature, which we would like to
implement atop CMAN.  We have already successfully implemented
experimental code using CMAN.

However, some of our customers are requiring a combination of
features that we believe we cannot currently satisfy with CMAN.

We need to provide:

  1. An at-least-once delivery guarantee.
  2. No need for our qpidd executable to be in the root group.

We can satisfy the at-least-once guarantee if our clustered
messaging brokers receive quorum-change messages in CPG order.
CMAN does that for us, but only at the cost of our processes
running with root-group privileges.

We can avoid the root-group privileges by using cmannotifyd, but
only at the cost of losing the CPG ordering guarantee.  If we use
cmannotifyd, and if one of our brokers fails, there will be a window
of time during which our cluster may lose messages.

Our ideal solution would be to use the CMAN interface as we are
now in our experimental code, but without the need to run with
root or root-group privileges.

Comment 2 Lon Hohberger 2012-06-28 20:37:00 UTC
rgmanager in STABLE32 (upstream) does something like this in msg_socket.c using SO_PEERCRED from getsockopt.  Then, each request is processed based on the permissions required.

rgmanager in this case simply differentiates read-only (less permission required - root gid) with read-write (more permission required - root uid).

However, the way it is set up, rgmanager mimics CMAN's permissions currently, I believe.

Comment 4 Fabio Massimo Di Nitto 2012-07-02 07:12:18 UTC
As originally discussed, this cannot and will not happen.


Note You need to log in before you can comment on or make changes to this bug.