Re: Announcing the Next Ubuntu Hug Day! - 19th of February, 2009

[David Orman]

Awesome, looking forward to this. I saw that in one bug tracker, the GTC
phase 2 auth support was made 'in progress'. Can't wait!

David

On Wed, Feb 18, 2009 at 2:45 AM, Rubén Romero y Cordero
wrote:

> Hi to you all,
>
> Tomorrow Ubuntu hug's day will be targetting the network-manager applet.
>
> It would be useful if some of you would join the efffort and aid
> people wanting to help make NM rock even harder!
>
> See you there!
>
> Regards,
>
> Rubén R.
> https://launchpad.net/~huayra 
>
> -- Forwarded message --
> From: Martin Mai 
> Date: Tue, 17 Feb 2009 16:58:42 +0100
> Subject: Announcing the Next Ubuntu Hug Day! - 19th of February, 2009
> To: ubuntu-bugsq...@lists.ubuntu.com,
> ubuntu-devel-annou...@lists.ubuntu.com, ubuntu-us...@lists.ubuntu.com,
> br...@ubuntu.com
>
> Fellow Ubuntu Triagers!
>
> This week's HugDay target is *drum roll please* network-manager-applet!
>  * #88 New bugs need a hug
>  * #23 Incomplete bugs need a status check
>  * #25 Confirmed bugs need a review
>
> Bookmark it, add it to your calendars, turn over those egg-timers!
>  * 19th of February, 2009
>  * http://wiki.ubuntu.com/UbuntuBugDay/20090219
>
> Can't stress it enough: everyone can help!
>
> Have some time? Triage boogz! I won't be upset if you get a headstart~ ;)
> Have a blog? Blog about Hugday!
> Have some screen space? Open #ubuntu-bugs and keep an eye out for
> newcomers in need.
> Have minions? Teach THEM to triage for you! :)
>
> Wanna be famous? Is easy! remember to use 5-A-day so if you do a good
> work your name could be listed at the top 5-A-Day Contributors in the
> Ubuntu Hall of Fame page!
>
> Make a difference; we will be in #ubuntu-bugs (FreeNode) all day and
> night, and will be ready to answer your questions about how to help.
>
> If you're new to all this, head to
>  http://wiki.ubuntu.com/HelpingWithBugs
>
> Have a nice day,
>   Martin Mai
> [From the BugSquad]
>
> ___
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>
>
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: PEAP with GTC in NetworkManager-0.7.0-0.12.svn4326.fc10.x86_64

[David Orman]

age 2
of 5 (Device Configure) starting...
Dec 11 23:51:08 localhost NetworkManager:   (wlan0): device state
change: 4 -> 5
Dec 11 23:51:08 localhost NetworkManager:   Activation
(wlan0/wireless): connection 'Auto SSIDWASHERE' has security, and secrets
exist.  No new secrets needed.
Dec 11 23:51:08 localhost NetworkManager:   Config: added 'ssid' value
'SSIDWASHERE'
Dec 11 23:51:08 localhost NetworkManager:   Config: added 'scan_ssid'
value '1'
Dec 11 23:51:08 localhost NetworkManager:   Config: added 'key_mgmt'
value 'WPA-EAP'
Dec 11 23:51:08 localhost NetworkManager:   Config: added 'password'
value ''
Dec 11 23:51:08 localhost NetworkManager:   Config: added 'eap' value
'PEAP'
Dec 11 23:51:08 localhost NetworkManager:   Config: added
'fragment_size' value '1300'
Dec 11 23:51:08 localhost NetworkManager:   Config: added 'phase1'
value 'peapver=1'
Dec 11 23:51:08 localhost NetworkManager:   Config: added 'phase2'
value 'auth=MD5'
Dec 11 23:51:08 localhost NetworkManager:   Config: added 'identity'
value 'USERNAMEWASHERE'
Dec 11 23:51:08 localhost NetworkManager:   Activation (wlan0) Stage 2
of 5 (Device Configure) complete.
Dec 11 23:51:08 localhost NetworkManager:   Config: set interface
ap_scan to 1
Dec 11 23:51:08 localhost NetworkManager:   (wlan0): supplicant
connection state:  disconnected -> scanning
Dec 11 23:51:12 localhost NetworkManager:   (wlan0): supplicant
connection state:  scanning -> associating
Dec 11 23:51:12 localhost NetworkManager:   (wlan0): supplicant
connection state:  associating -> disconnected
Dec 11 23:51:12 localhost NetworkManager:   (wlan0): supplicant
connection state:  disconnected -> associated
Dec 11 23:51:27 localhost NetworkManager:   wlan0: link timed out.
Dec 11 23:51:33 localhost NetworkManager:   Activation
(wlan0/wireless): association took too long.
Dec 11 23:51:33 localhost NetworkManager:   (wlan0): device state
change: 5 -> 6
Dec 11 23:51:33 localhost NetworkManager:   Activation
(wlan0/wireless): asking for new secrets
Dec 11 23:51:33 localhost NetworkManager:   (wlan0): supplicant
connection state:  associated -> disconnected
Dec 11 23:51:38 localhost NetworkManager:   (wlan0): supplicant
connection state:  disconnected -> scanning
Dec 11 23:51:41 localhost NetworkManager:   (wlan0): supplicant
connection state:  scanning -> disconnected
Dec 11 23:51:41 localhost NetworkManager:   (wlan0): supplicant
connection state:  disconnected -> associated
Dec 11 23:51:41 localhost NetworkManager:   (wlan0): supplicant
connection state:  associated -> disconnected
Dec 11 23:51:43 localhost NetworkManager:   (wlan0): supplicant
connection state:  disconnected -> associated
Dec 11 23:51:43 localhost NetworkManager:   (wlan0): supplicant
connection state:  associated -> disconnected

>From the wpa_supplicant.log:

Trying to associate with MACADDIEWASHERE (SSID='SSIDWASHERE' freq=24xx MHz)
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Associated with MACADDIEWASHERE
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
EAP-PEAP: Failed to select forced PEAP version 1
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
*snip snip, lots more remove keys*

[r...@ormandj-laptop log]# rpm -qa |grep wpa_supplicant
wpa_supplicant-0.6.4-2.fc10.x86_64
[r...@ormandj-laptop log]#

[r...@ormandj-laptop log]# rpm -qa |grep Network
NetworkManager-gnome-0.7.0-0.12.svn4326.fc10.x86_64
NetworkManager-glib-0.7.0-0.12.svn4326.fc10.x86_64
NetworkManager-0.7.0-0.12.svn4326.fc10.x86_64
NetworkManager-vpnc-0.7.0-0.11.svn4326.fc10.x86_64
NetworkManager-openvpn-0.7.0-16.svn4326.fc

Re: PEAP with GTC in NetworkManager-0.7.0-0.12.svn4326.fc10.x86_64

[David Orman]

Hi Dan,

Here's some more information about PEAP-GTC.

First, a little snippit from the freeradius project:
http://wiki.freeradius.org/EAP#PEAPv1.2FEAP-GTC
It references the RFC in which PEAP-GTC is defined as an inner
authentication protocol: http://www.ietf.org/rfc/rfc3748.txt
In the RFC, the relevant section is 5.6

In our environment, we utilize RSA tokens with a randomly generated keys, so
I think it is likely the method you are thinking of. You're correct in your
analysis, it would certainly be an always prompt/never save bit in the
application. Running a search to gather more information to help out, all I
ran into were posts about people who had upgraded various distributions and
gotten NM 0.7.x (that had been running 0.6.x with working PEAP-GTC support),
so it does seem to be utilized somewhat frequently. wpa_supplicant appears
to still work correctly with PEAP-GTC for most people, as does NM 0.6.x, so
most people who are in the same boat as I am have been downgrading to the
older version of NM or just using wpa_supplicant directly.

I'm happy to assist however I can in this, but I will likely be limited to
providing myself as a lab rat for testing changes. Anybody is more than
welcome to take me up on that offer. :) Let me know if there is any other
information I can gather that would help out, and thank you for looking into
this!

Cheers,
David

On Fri, Dec 19, 2008 at 10:15 AM, Dan Williams  wrote:

> On Thu, 2008-12-18 at 23:17 -0600, David Orman wrote:
> > Filed a bug in Gnome's bugtracker in case anybody else runs across
> > this thread with the same issue:
> > http://bugzilla.gnome.org/show_bug.cgi?id=565065
>
> The GTC is the dongle thing that gives you a one-time-pad, correct?  In
> this case, we do need to add a bunch of support for GTC to
> NetworkManager.  It would mean not entering the PIN in the connection
> editor or anywhere, but having the applet ask for the PIN *ever* time
> the connection or reconnection attempt was made.  It wouldn't be hard to
> actually support, but would take some code.  It's on the table, I've
> seen another request for it recently, just needs the work done.  If
> anyone's up for doing the patch, I can outline what needs to get
> changed.
>
> Dan
>
> > Thanks,
> > David
> >
> > On Thu, Dec 18, 2008 at 4:09 AM, David Orman 
> > wrote:
> > Hi,
> >
> > I am trying to use Fedora 10/Intel 5300 on a Cisco based
> > wireless network, which uses GTC for the inner authentication.
> > I see this option no longer exists in the version of NM that I
> > have: NetworkManager-0.7.0-0.12.svn4326.fc10.x86_64.
> >
> > Out of curiosity, I used GIT to get the latest source, and see
> > the following in libnm-util/nm-setting-8021x.c:
> >
> >  950 { "gtc", NULL, NULL },  // FIXME: implement
> >
> > So, it appears GTC is not implemented in NM, even though
> > wpa_supplicant supports it. Are there any patches available
> > that allow this to work? This seems to be a regression from
> > version 0.6.x (I don't know the exact version I was using
> > before).
> >
> > I've seen various bugs filed at the distribution level
> > regarding this, but I didn't see one with this specific
> > problem in the Gnome bugtracker. However, seeing the comment
> > in the source, it seems to be a known-issue. Is this actually
> > the case, and will this actually be implimented? Do I need to
> > actually file a bug? Are there any known workarounds?
> >
> > Respectfully,
> > David
> >
> > ___
> > NetworkManager-list mailing list
> > NetworkManager-list@gnome.org
> > http://mail.gnome.org/mailman/listinfo/networkmanager-list
>
>
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: PEAP with GTC in NetworkManager-0.7.0-0.12.svn4326.fc10.x86_64

[David Orman]

Filed a bug in Gnome's bugtracker in case anybody else runs across this
thread with the same issue: http://bugzilla.gnome.org/show_bug.cgi?id=565065

Thanks,
David

On Thu, Dec 18, 2008 at 4:09 AM, David Orman  wrote:

> Hi,
>
> I am trying to use Fedora 10/Intel 5300 on a Cisco based wireless network,
> which uses GTC for the inner authentication. I see this option no longer
> exists in the version of NM that I have:
> NetworkManager-0.7.0-0.12.svn4326.fc10.x86_64.
>
> Out of curiosity, I used GIT to get the latest source, and see the
> following in libnm-util/nm-setting-8021x.c:
>
>  950 { "gtc", NULL, NULL },  // FIXME: implement
>
> So, it appears GTC is not implemented in NM, even though wpa_supplicant
> supports it. Are there any patches available that allow this to work? This
> seems to be a regression from version 0.6.x (I don't know the exact version
> I was using before).
>
> I've seen various bugs filed at the distribution level regarding this, but
> I didn't see one with this specific problem in the Gnome bugtracker.
> However, seeing the comment in the source, it seems to be a known-issue. Is
> this actually the case, and will this actually be implimented? Do I need to
> actually file a bug? Are there any known workarounds?
>
> Respectfully,
> David
>
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

PEAP with GTC in NetworkManager-0.7.0-0.12.svn4326.fc10.x86_64

[David Orman]

Hi,

I am trying to use Fedora 10/Intel 5300 on a Cisco based wireless network,
which uses GTC for the inner authentication. I see this option no longer
exists in the version of NM that I have:
NetworkManager-0.7.0-0.12.svn4326.fc10.x86_64.

Out of curiosity, I used GIT to get the latest source, and see the following
in libnm-util/nm-setting-8021x.c:

 950 { "gtc", NULL, NULL },  // FIXME: implement

So, it appears GTC is not implemented in NM, even though wpa_supplicant
supports it. Are there any patches available that allow this to work? This
seems to be a regression from version 0.6.x (I don't know the exact version
I was using before).

I've seen various bugs filed at the distribution level regarding this, but I
didn't see one with this specific problem in the Gnome bugtracker. However,
seeing the comment in the source, it seems to be a known-issue. Is this
actually the case, and will this actually be implimented? Do I need to
actually file a bug? Are there any known workarounds?

Respectfully,
David
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list