[Fwd: PEAP and keyfile]
Jerry Vonau
jvonau at shaw.ca
Fri Aug 16 20:43:45 EDT 2013
Hi All,
In 13.1.0 [1] were used while 13.2.0 uses [2].
Any ideas on how to solve this one? Next week I'll try replacing the
non-working connection file with the one that does work when I have
access to that network again.
Jerry
-------- Forwarded Message --------
From: Jerry Vonau <jvonau at shaw.ca>
To: networkmanager-list at gnome.org
Subject: PEAP and keyfile
Date: Fri, 16 Aug 2013 19:31:20 -0500
Hi All:
I've ran into a situation that I'm not sure in how to handle with these
packages[1] I was able to use nm-connection-editor with only the keyfile
plugin to create the system connection with ease and resulted in this
configuration:
[802-1x]
eap=peap;
identity=xxxxx
phase2-auth=mschapv2
password=yyyyy
[802-11-wireless-security]
key-mgmt=wpa-eap
After updating the rpms[2] using nm-connection-editor results in this
configuration:
[802-11-wireless-security]
key-mgmt=wpa-eap
[802-1x]
eap=peap;
identity=xxxxx
phase2-auth=mschapv2
password-flags=1
system-ca-certs=true
I'm at a bit of a loss as to what to do about this, any help or pointers
would be grateful. I understand that password-flags=1 hands this over to
an auth agent for the secrets, gnome keyring is running but with an
empty password. I clicked ignore when prompted for the certs file. I've
tried to downgrade back to [1] but with the same results. Am I running
into some polkit issue here? What other dependencies might I have to
downgrade to return to the same functionality?
Thank,
Jerry
1.
NetworkManager-0.9.7.0-8.git20121004.fc18.armv7hl
network-manager-applet-0.9.7.0-4.git20121016.fc18.armv7hl
NetworkManager-glib-0.9.7.0-8.git20121004.fc18.armv7hl
nm-connection-editor-0.9.7.0-4.git20121016.fc18.armv7hl
2.
NetworkManager-0.9.8.1-3.git20130514.fc18.armv7hl
network-manager-applet-0.9.8.1-3.git20130430.fc18.armv7hl
NetworkManager-glib-0.9.8.1-3.git20130514.fc18.armv7hl
nm-connection-editor-0.9.8.1-3.git20130430.fc18.armv7hl
More information about the Devel
mailing list