Bug 833199

Summary: [ifcfg-rh] WPA-LEAP connections cannot be made system connections
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: urgent Docs Contact:
Priority: urgent    
Version: 6.3CC: hesemeyt, jreed, jwest, mgordon, ngalvin, tpelka
Target Milestone: rcKeywords: ZStream
Target Release: 6.3   
Hardware: All   
OS: Linux   
Fixed In Version: NetworkManager-0.8.1-37.el6 Doc Type: Bug Fix
Doc Text:
Due to a bug reading and writing network configuration files, network connections using the LEAP authentication method could not be made available to all users. A patch has been provided to address this issue and the network configuration files now allow LEAP as expected.
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-21 10:34:50 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:
Bug Depends On:    
Bug Blocks: 782183, 837401, 840699, 864828    
Description Flags
Backport of EAP-LEAP fixes for ifcfg-rh none

Description Dan Williams 2012-06-18 20:58:42 UTC
A bug in the ifcfg reader or writer code doesn't allow LEAP as an auth method in IEEE_8021X_EAP_METHODS.  We need a backport of af7e26b39af6598556eee2bcba23505cb6709ad9 to handle this correctly.

Comment 1 Dan Williams 2012-06-18 21:11:41 UTC
Created attachment 592749 [details]
Backport of EAP-LEAP fixes for ifcfg-rh

Comment 2 RHEL Product and Program Management 2012-07-16 22:50:34 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 11 errata-xmlrpc 2013-02-21 10:34:50 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.