Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
In oscap-ssh man page, there is example, how to prepare user for passwordless running of oscap via sudo.
----
like /etc/sudoers.d/99-oscap-user:
# allow oscap-user to run openscap scanner
Defaults!/bin/oscap !requiretty
oscap-user ALL=(root) NOPASSWD: /bin/oscap
----
oscap binary does not dwell in /bin/ directory, but /usr/bin/ - thus making the example not copypasteble and slightly less useful for less knowledgeable user.
Version-Release number of selected component (if applicable):
openscap-1.2.8-1.el6
Fixed in version openscap-utils-1.2.12-1.el6:
[0 root@qeos-35 ~]# rpm -qa openscap-utils; man oscap-ssh | grep -A 3 99-oscap-user
openscap-utils-1.2.12-1.el6.x86_64
adding a file like /etc/sudoers.d/99-oscap-user:
# allow oscap-user to run openscap scanner
Defaults!/usr/bin/oscap !requiretty
oscap-user ALL=(root) NOPASSWD: /usr/bin/oscap
[0 root@qeos-35 ~]# which oscap
/usr/bin/oscap
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://rhn.redhat.com/errata/RHBA-2017-0754.html
Description of problem: In oscap-ssh man page, there is example, how to prepare user for passwordless running of oscap via sudo. ---- like /etc/sudoers.d/99-oscap-user: # allow oscap-user to run openscap scanner Defaults!/bin/oscap !requiretty oscap-user ALL=(root) NOPASSWD: /bin/oscap ---- oscap binary does not dwell in /bin/ directory, but /usr/bin/ - thus making the example not copypasteble and slightly less useful for less knowledgeable user. Version-Release number of selected component (if applicable): openscap-1.2.8-1.el6