Red Hat Bugzilla – Full Text Bug Listing
|Summary:||audit: increase the maximum length of the key field|
|Product:||Red Hat Enterprise Linux 5||Reporter:||Alexander Viro <aviro>|
|Component:||kernel||Assignee:||Alexander Viro <aviro>|
|Status:||CLOSED ERRATA||QA Contact:||Red Hat Kernel QE team <kernel-qe>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2009-09-02 04:54:06 EDT||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Alexander Viro 2008-12-08 02:16:57 EST
Key lengths were arbitrarily limited to 32 characters. If userspace is going to start using the single kernel key field as multiple virtual key fields (example key=key1,key2,key3,key4) we should give them enough room to work. Mainline kernel has that limit raised to 255; we need that change in rhel5.4 (upstream patch applies verbatim).
Comment 1 RHEL Product and Program Management 2009-01-27 15:38:32 EST
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Comment 2 RHEL Product and Program Management 2009-02-16 10:45:39 EST
Updating PM score.
Comment 3 Don Zickus 2009-02-23 15:03:00 EST
in kernel-2.6.18-132.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5 Please do NOT transition this bugzilla state to VERIFIED until our QE team has sent specific instructions indicating when to do so. However feel free to provide a comment indicating that this fix has been verified.
Comment 8 errata-xmlrpc 2009-09-02 04:54:06 EDT
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2009-1243.html