Bug 834444

Summary: Enable Proactive Key Caching for all WPA-Enterprise configurations
Product: Red Hat Enterprise Linux 6 Reporter: Dan Williams <dcbw>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: urgent    
Version: 6.3CC: jreed, jwest, mgordon, ngalvin, tpelka, walicki
Target Milestone: rcKeywords: ZStream
Target Release: 6.3   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: NetworkManager-0.8.1-37.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-21 10:34:56 UTC Type: Bug
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:    
Bug Blocks: 782183, 837401, 840699, 864831    
Attachments:
Description Flags
Always use OKC for WPA Enterprise configs none

Description Dan Williams 2012-06-21 21:47:50 UTC
RHEL 6.2 enabled PKC/OKC for EAP-GTC, but we really want to enable it for all WPA-Enterprise configurations, since all those benefit greatly from OKC too.

Comment 1 John Walicki 2012-06-22 03:26:53 UTC
The internal IBM Linux deployment team is interested in this patch.

Comment 2 Dan Williams 2012-07-03 19:54:31 UTC
Created attachment 596088 [details]
Always use OKC for WPA Enterprise configs

Comment 3 Dan Williams 2012-07-03 19:55:41 UTC
(In reply to comment #1)
> The internal IBM Linux deployment team is interested in this patch.

See also the fixes for wpa_supplicant in bug 813579.

Comment 4 RHEL Program Management 2012-07-16 22:50:00 UTC
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release.  Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.

Comment 12 errata-xmlrpc 2013-02-21 10:34:56 UTC
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.

http://rhn.redhat.com/errata/RHBA-2013-0429.html