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 1534030 - no option to set user/group
Summary: no option to set user/group
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nuxwdog
Version: 7.5
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Ade Lee
QA Contact: Asha Akkiangady
URL:
Whiteboard:
Depends On: 1523410
Blocks: 1540092
TreeView+ depends on / blocked
 
Reported: 2018-01-12 20:51 UTC by Ade Lee
Modified: 2018-07-03 16:51 UTC (History)
10 users (show)

Fixed In Version: nuxwdog-1.0.3-7.el7
Doc Type: Enhancement
Doc Text:
Feature: A new option has been added to allow deployers to specify the user that the process spawned by nuxwdog will run as. Reason: When nuxwdog is invoked by systemd, it prompts for passwords using systemd-ask-password, but needs to be run as a privileged user to be able to access the tty-agent used by systemctl. Without this change, nuxwdog would then spawn the real server process as this privileged user, which is a security risk. With this change, deployers can direct nuxwdog to spawn the real process using a specified user. Result: Deployers can add directive "User foo" to their nuxwdog.conf file. (foo is the username). The process spawned should be run as that user.
Clone Of:
: 1540092 (view as bug list)
Environment:
Last Closed: 2018-04-10 18:15:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0971 0 None None None 2018-04-10 18:15:35 UTC

Description Ade Lee 2018-01-12 20:51:04 UTC 
Description of problem:

Nuxwdog should provide options to set the uid and gid of the process being spawned.  Right now, it only sets as the same user as nuxwdog - which is in the pki case, root. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 Ade Lee 2018-01-17 16:36:13 UTC 
commit 3d7adfbe0788f33a67c3ed65e12ba9d32074a674 (origin/master, origin/HEAD, gerrit/master, master)
Author: Ade Lee <alee>
Date:   Mon Jan 15 15:25:36 2018 -0500

    Add parameter to set the uid of the invoked process
Comment 4 Ade Lee 2018-01-17 17:23:29 UTC 
QE Verification:

This is most easily - and most usefully verified as part of the verfication for https://bugzilla.redhat.com/show_bug.cgi?id=1523410

You should be able to -
1) Use pkispawn to create an instance (either using a new user or the default pkiuser)  For convenience I will use pki-tomcat as my insatnce name.
3)Shut down the instance
   systemctl stop pki-tomcatd
2) Enable nuxwdog for that instance:  
   pki-server instance-nuxwdog-enable pki-tomcat
3) Confirm that the instance's nuxwdog.conf file contains User foo
  where foo is pkiuser or whatever your user was
   cat /etc/pki/pki-tomcat/nuxwdog.conf
4) Start the instance and enter passwords.  Confirm that the instance is running 
   as the foo user.
   
   systemctl restart pki-tomcatd-nuxwdog
   ps -ef |grep nuxwdog 

   Note: the nuxwdog process will run a root, but tomcat will run as nuxwdog.
Comment 8 Roshni 2018-02-07 21:41:10 UTC 
[root@nocp1 ~]# rpm -qi nuxwdog
Name        : nuxwdog
Version     : 1.0.3
Release     : 7.el7
Architecture: x86_64
Install Date: Fri 26 Jan 2018 02:34:55 PM EST
Group       : System Environment/Libraries
Size        : 103675
License     : LGPLv2 and (GPL+ or Artistic)
Signature   : RSA/SHA256, Mon 22 Jan 2018 09:33:10 PM EST, Key ID 199e2f91fd431d51
Source RPM  : nuxwdog-1.0.3-7.el7.src.rpm
Build Date  : Mon 22 Jan 2018 09:12:21 PM EST
Build Host  : x86-041.build.eng.bos.redhat.com
Relocations : (not relocatable)
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
Vendor      : Red Hat, Inc.
URL         : http://www.redhat.com/certificate_system
Summary     : Watchdog server to start and stop processes, and prompt for passwords

Verification steps in comment 4
Comment 11 errata-xmlrpc 2018-04-10 18:15:15 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0971
Note You need to log in before you can comment on or make changes to this bug.