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:
It would be nice to be able to easily query the security plugin for the severity of a given errata. I realize its in the title, but scheduling downtime for applications which must be restarted afterwards is easier when I can build an automated query to report which errata are critical and which are less so. For the critical ones I'd probably be able to schedule a window in the very very near future, for the others I don't have that luxury.
Version-Release number of selected component (if applicable): 1.1.30-6.el6
How reproducible: always
Steps to Reproduce:
1. yum list-sec
2. look for Critical (or use grep)
3. wish this was able to be contained in the updateinfo.xml so that my way of rating vulnerabilities doesn't depend on you never changing the formatting of the title.
Actual results:
A weird hack for determining importance of updates.
Expected results:
A more elegant way of knowing how severe a security update is
Additional info:
In fedora this doesn't bother me so much as that is never on my servers, but with yum-plugin-security being such a great tool. I'd love to leverage it some more for manager friendly reporting.
Comment 2RHEL Program Management
2011-11-01 05:47:51 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
The latest version of the security plugin has --sec-severity option. This should already be fixed/available in the version you have.
Also note that there is a:
yum updateinfo
...command, see the man page.