Hide Forgot
A patch for sudo-1.8.19 has already been posted: https://www.sudo.ws/repos/sudo/rev/e7a74f3dfa56
Description of problem: 1. Proposed title of this feature request: Provide a config option for sudo-io logfiles ownership and permissions 3. What is the nature and description of the request? Customer needs to have the sudo-io logging that: * belong to one specific group * have specific permission (readable by group) 4. Why does the customer need this? (List the business requirements here) They have Splunk SIEM and they are using the agent from non-root account (splunk). This agent needs to collect log files. 5. How would the customer like to achieve this? (List the functional requirements here) Settings to be add in the sudoers (param name = default value): iolog_umask=0700 iolog_user=root iolog_group=root 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. - enable setting/change default setting - use sudo with 2 users 2 times each - check permissions on sudo-io log files (i.e. /var/log/sudo-io/ and subdirs) 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? Topic has been raised already upstream https://www.sudo.ws/pipermail/sudo-users/2016-October/005846.html 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? RHEL7 9. Is the sales team involved in this request and do they have any additional input? No 10. List any affected packages or components. sudo 11. Would the customer be able to assist in testing this functionality if implemented? Yes Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This feature will be delivered in rhel 7.4 by rebase. It is now available in testing copr build sudo-1.8.19p2-1.el7.
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-2017:2017