Re: Leap authentication problem in NM.- once again



----- "Aaron Konstam" <akonstam sbcglobal net> wrote:

> > Looking at the applet code, I'm suspicious that the 6.5 changes that 
> > broke some WPA2 configs have done the same to LEAP. So we might just> 
> > need to extend that last patch to include LEAP networks.
> > 
> > Aaron, does your LEAP passphrase get stored in the keyring or in gconf? 
> > You might need to install the gnome-keyring-manager to check the 
> > keyring. If it's in the keyring then I would expect it only to work when 
> > you enter all the information through the applet, but not when it 
> > re-connects? If this is the case then it is the issue above & should be 
> > a simple fix...
> > 
> > Regards,
> > Jon
>
> Yes the passphrase gets stored in the gnome-keyring. The problem is
> exactly as you describe it. It last worked in the Unstable CVS version
> last September which was probably 6.4

The attached patch should allow fetching the LEAP passphrase from the keyring. I'm assuming it's always stored there for LEAP networks and doesn't need a conditional check like the WPA2 case.

Regards,
Jon.
diff -urN NetworkManager-0.6.5/nm-applet-0.6.5/src/applet-dbus-info.c NetworkManager-0.6.5.new/nm-applet-0.6.5/src/applet-dbus-info.c
--- NetworkManager-0.6.5/nm-applet-0.6.5/src/applet-dbus-info.c	2007-06-07 17:44:06.000000000 +0100
+++ NetworkManager-0.6.5.new/nm-applet-0.6.5/src/applet-dbus-info.c	2007-07-06 15:11:16.000000000 +0100
@@ -193,9 +193,7 @@
 	}
 
 	/* Hack: 802.1x passwords are not stored in the keyring */
-	if (!new_key &&
-		((we_cipher == NM_AUTH_TYPE_WPA_EAP && !have_priv_key_file) ||
-		we_cipher == NM_AUTH_TYPE_LEAP))
+	if (!new_key && (we_cipher == NM_AUTH_TYPE_WPA_EAP && !have_priv_key_file))
 	{
 		NMGConfWSO *gconf_wso;
 		gconf_wso = nm_gconf_wso_new_deserialize_gconf (applet->gconf_client,


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]