Bug 1540092
| Summary: | no option to set user/group [rhel-7.4.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | nuxwdog | Assignee: | Ade Lee <alee> |
| Status: | CLOSED ERRATA | QA Contact: | Asha Akkiangady <aakkiang> |
| Severity: | urgent | Docs Contact: | Marc Muehlfeld <mmuehlfe> |
| Priority: | urgent | ||
| Version: | 7.5 | CC: | alee, cfu, edewata, ftweedal, jmagne, lmiksik, mharmsen, msauton, nkinder, rpattath |
| Target Milestone: | rc | Keywords: | Reopened, ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | nuxwdog-1.0.3-5.1.el7_4 | Doc Type: | Enhancement |
| Doc Text: |
During the start of the service, systemd uses the systemd-ask-password utility to prompt for the password. However this process needs to run as a privileged user to be able to access the TTY agent used by the systemctl utility. Previously, the nuxwdog service spawned the real server process as this privileged user, which was a security risk. With this update, administrators can now configure to spawn the real process using the account set in the "User" parameter in the /var/lib/pki/<instance_name>/conf/nuxwdog.conf file, which solves the security risk.
|
Story Points: | --- |
| Clone Of: | 1534030 | Environment: | |
| Last Closed: | 2018-04-17 16:19:29 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1534030 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2018-01-30 09:25:51 UTC
From the RHEL 7.5 bug that this was cloned from: 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. [root@auto-hv-01-guest01 ~]# rpm -qi pki-ca Name : pki-ca Version : 10.4.1 Release : 18.el7_4 Architecture: noarch Install Date: Wed 14 Mar 2018 05:09:18 PM EDT Group : System Environment/Daemons Size : 2359969 License : GPLv2 Signature : (none) Source RPM : pki-core-10.4.1-18.el7_4.src.rpm Build Date : Thu 15 Feb 2018 01:45:06 PM EST Build Host : ppc-035.build.eng.bos.redhat.com Relocations : (not relocatable) Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> Vendor : Red Hat, Inc. URL : http://pki.fedoraproject.org/ Summary : Certificate System - Certificate Authority Verification steps as explained in comment 4. 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:1139 |