Launchpad has imported 15 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=451027.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2008-06-12T14:19:07+00:00 Major wrote:

Description of problem:
GTC encapsulation support is unavailable when you choose WPA2 -> PEAP in 
NetworkManager.  Only 
MSCHAP/v2 and CHAP are shown, even though GTC is included in wpa_supplicant.  
The same versions 
of NetworkManager on other distributions includes support for GTC.

Version-Release number of selected component (if applicable):
NetworkManager-0.7.0-0.6.7.svn3370.fc8 (Fedora 8)

Steps to Reproduce:
1. Click NetworkManager applet in GNOME
2. Choose a WPA-2 network
3. Choose LEAP
4. GTC is unavailable
  
Actual results:
GTC does not appear as a selection

Expected results:
GTC should appear as a selection

Additional info:
GTC is already included in wpa_supplicant, but is mysteriously missing in 
NetworkManager

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/284211/comments/0

------------------------------------------------------------------------
On 2008-08-11T17:56:30+00:00 Dan wrote:

Some of the infrastructure is not there yet, but support for this should
be coming in the future.  Not sure how long.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/284211/comments/1

------------------------------------------------------------------------
On 2008-09-23T05:00:15+00:00 S. wrote:

Looking at nm-supplicant-settings-verify.c, taken from 
NetworkManager-0.7.0-0.11.svn4022.fc8.src.rpm, I see:
const char * phase2_allowed[] =   {"auth=PAP", "auth=CHAP", "auth=MSCHAP",
                                   "auth=MSCHAPV2", "auth=GTC", "auth=OTP",
                                   "auth=MD5", "auth=TLS", "autheap=MD5",
                                   "autheap=MSCHAPV2", "autheap=OTP",
                                   "autheap=GTC", "autheap=TLS", NULL };
But I'm not seeing GTC as an option for PEAP (nor TTLS). The last discussion 
regarding GTC support I'm finding on the networkmanager-list archives is from 
early 2007. Is there more still needed to be done or other configure options 
needed? Willing to help, unsure where to start.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/284211/comments/2

------------------------------------------------------------------------
On 2008-11-26T10:51:40+00:00 Bug wrote:


This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/284211/comments/7

------------------------------------------------------------------------
On 2009-01-09T06:35:44+00:00 Bug wrote:


Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/284211/comments/15

------------------------------------------------------------------------
On 2009-02-18T02:47:39+00:00 James wrote:

This "Bug" (or lack of a feature) is still present in F10.  I think it
was available in on older version, but I'm not sure.

related: http://bugzilla.gnome.org/show_bug.cgi?id=565065

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/284211/comments/20

------------------------------------------------------------------------
On 2009-02-18T11:18:16+00:00 Dan wrote:

*** Bug 474723 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/284211/comments/21

------------------------------------------------------------------------
On 2009-07-29T18:23:20+00:00 Dan wrote:

Fixed upstream in :

272c6a626a27f4d3a88a1aedd7887d63f6a818d5 (nm master)
272cf183c7963dfaf019b2f5afc816c0bd2dfd73 (applet master)

272c6a626a27f4d3a88a1aedd7887d63f6a818d5 (nm 0.7)
0461fff8039ce612fb5a50ce760b782f62457d59 (applet 0.7)

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/284211/comments/32

------------------------------------------------------------------------
On 2009-09-22T21:00:31+00:00 Ravikiran wrote:

Is there any chance we can get an update for F-11? If not, would it be
possible to rebuild the current 20090708 rpm after updating the sources
to the 0.7 branch head (on both nm and applet), i.e., is the source on
the 0.7 branch similar enough that the current spec file will work?

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/284211/comments/38

------------------------------------------------------------------------
On 2009-09-23T08:32:48+00:00 Dan wrote:

Yeah, we'll get an update for F10 and F11 soon here.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/284211/comments/39

------------------------------------------------------------------------
On 2009-11-02T16:57:28+00:00 Dan wrote:

Fix has actually been in updates-testing for a bit...

F11 update:

https://admin.fedoraproject.org/updates/F11/FEDORA-2009-10696

F10 update:

https://admin.fedoraproject.org/updates/F10/FEDORA-2009-10546

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/284211/comments/40

------------------------------------------------------------------------
On 2009-11-04T12:34:00+00:00 Fedora wrote:

NetworkManager-0.7.1.998-1.fc11, 
mobile-broadband-provider-info-1.20090918-1.fc11 has been pushed to the Fedora 
11 testing repository.  If problems still persist, please make note of it in 
this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update NetworkManager 
mobile-broadband-provider-info'.  You can provide feedback for this update 
here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-10696

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/284211/comments/41

------------------------------------------------------------------------
On 2009-11-18T10:13:18+00:00 Bug wrote:


This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/284211/comments/42

------------------------------------------------------------------------
On 2009-12-07T07:35:23+00:00 Fedora wrote:

mobile-broadband-provider-info-1.20090918-1.fc11,
NetworkManager-0.7.2-1.fc11 has been pushed to the Fedora 11 stable
repository.  If problems still persist, please make note of it in this
bug report.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/284211/comments/43

------------------------------------------------------------------------
On 2009-12-18T06:12:55+00:00 Bug wrote:


Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/284211/comments/44


** Changed in: network-manager-applet (Fedora)
   Importance: Unknown => Medium

** Changed in: network-manager (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/284211

Title:
  [intrepid] network-manager-gnome 0.7 missing PEAP-GTC option

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager package in Fedora:
  Won't Fix
Status in network-manager-applet package in Fedora:
  Won't Fix

Bug description:
  Binary package hint: network-manager-gnome

  Using Intrepid (beta, up-to-date) on multiple laptops,  also is an
  issue on the release version of Intrepid.

  network-manager-gnome 0.7~~svn20081015t194645-0ubuntu1 doesn't have
  the option to choose GTC for inner authentication when using
  IEEE8021.x or WPA2 Enterprise. Only MSCHAPv2 and MD5 supported.

  This is a regression from Hardy (network-manager-gnome 0.6.6) which
  supports PEAP-GTC just fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/284211/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to