knetworkmanager does not save password for WPA enterprise

Bug #90138 reported by smidl
16
Affects Status Importance Assigned to Milestone
knetworkmanager (Suse)
Fix Released
Medium
knetworkmanager (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: knetworkmanager

Typically, knetworkmanager uses kwallet to store passwords. It works very well for WEP keys but it doesn't for WAP Enterprise.

When I connect to WAP Enterprise, knm remembers the network (in Options>Show Networks) but it does not create an entry in kwallet (Kwalletmanager does not show it in knetworkmanager branch).
So, when knm attempts to connect to the network next time, it goes to infinite loop (or Very long timeout?).

Workaround:
1) Delete the saved network in Options>Show Networks
2) Switch to offline
3) Switch to online
4) connect to the same network
this time the dialog for entering the password pups-up.

Revision history for this message
Anthony Mercatante (tonio) wrote :

That's a well known issue between kwallet and kdeinit.
It is fixed in feisty, since kwallet now writes all entries immediatly instead of on logout.

Changed in knetworkmanager:
status: Unconfirmed → Fix Released
Revision history for this message
smidl (vasek-smidl) wrote : Re: [Bug 90138] Re: knetworkmanager does not save password for WPA enterprise

I am running the latest update (1 hour ago) from Feisty repositories
and the problem remains. I guess it has different cause.

WEP keys do appear in kwalletmanager immediatelly after log in to the network.
However, WAP Enterprise never appears in kwalletmanager.

Is there any log I should provide?

On 3/7/07, Anthony Mercatante <email address hidden> wrote:
> That's a well known issue between kwallet and kdeinit.
> It is fixed in feisty, since kwallet now writes all entries immediatly instead of on logout.
>
> ** Changed in: knetworkmanager (Ubuntu)
> Status: Unconfirmed => Fix Released
>
> --
> knetworkmanager does not save password for WPA enterprise
> https://launchpad.net/bugs/90138
>

Revision history for this message
dystopianray (dystopianray) wrote :

I have the same problem on edgy and fiesty with latest knetworkmanager updates.

WPA Enterprise passwords are never stored in kwallet but it saves all the other network settings in knetworkmanagerrc. When knetworkmanager automatically tries to connect to the network again it always fails because it is supplying all details except the password to wpa_supplicant. It should store the password in kwallet and retrieve it from there or at least prompt the user to supply the needed password.

The passwords for WPA-PSK and WEP networks are stored in kwallet without issue, it is only WPA Enterprise that I have encountered where the passwords are not stored.

I must manually remove the WPA Enterprise network config from knetworkmanagerrc and re-enter the network details each time I want to connect to an enterprise network, it is very inconvenient.

Revision history for this message
dystopianray (dystopianray) wrote :

This bug is not fixed and is still an issue in the latest packages on edgy and feisty.

Changed in knetworkmanager:
status: Fix Released → Unconfirmed
Revision history for this message
dystopianray (dystopianray) wrote :

I have created a patch based on the latest knetworkmanager in feisty which should save and restore the WPA-EAP password correctly. I would appreciate it if somebody could take a look at it and try it out. Hopefully this can be fixed before feisty is released.

I have attached the patch to this comment.

Changed in knetworkmanager:
status: Unknown → Confirmed
Changed in knetworkmanager:
status: Confirmed → In Progress
Revision history for this message
Anthony Mercatante (tonio) wrote :

I uploaded a new package with that fix in it.
I can't test myself, so thanks for feedback quick so that I can drop the patch in case it doesn't work.
Reports against that patch at suse BTS seems to show it is better, doesn't break anything, but doesn't work on restaure.
Waiting for your feedback guys !

Changed in knetworkmanager:
status: Unconfirmed → In Progress
Revision history for this message
dystopianray (dystopianray) wrote :

I tested the package with the fix and can confirm that it isn't working properly.

The password is saved into kwallet correctly when you initially connect to the network. However, on subsequent attempts to connect it is not retrieving the password from kwallet.

Revision history for this message
smidl (vasek-smidl) wrote :

Same behaviour here. Password is written into kwallet but it is not
retrieved correctly.

On 4/4/07, dystopianray <email address hidden> wrote:
> I tested the package with the fix and can confirm that it isn't working
> properly.
>
> The password is saved into kwallet correctly when you initially connect
> to the network. However, on subsequent attempts to connect it is not
> retrieving the password from kwallet.
>
> --
> knetworkmanager does not save password for WPA enterprise
> https://bugs.launchpad.net/bugs/90138
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
dystopianray (dystopianray) wrote :

Attached is a modified patch from the Novell Bugzilla which may fix the issue of knetworkmanager not restoring the password from the kwallet. I can test this if a build is provided.

Revision history for this message
dystopianray (dystopianray) wrote :

My apologies, the patch was just modified further on the Novell Bugzilla and this third patch seems to be a better fix for this issue and also fixes Novell Bug #253414

https://bugzilla.novell.com/show_bug.cgi?id=253414

Changed in knetworkmanager:
status: In Progress → Fix Released
Revision history for this message
Luka Renko (lure) wrote :

Debdiff with latest patch from OpenSUSE that should fix this finally.

Revision history for this message
Anthony Mercatante (tonio) wrote :

Uploaded, thanks Luka

Changed in knetworkmanager:
status: In Progress → Fix Released
Revision history for this message
smidl (vasek-smidl) wrote :

The new package works all right for me.
Many thanks gentlemen.
Vasek

Revision history for this message
Charlie Figura (cfigura) wrote :

I've been having this problem under feisty with the knetworkmanager 0.2 with KDE 3.5.8.
Can this patch be applied to the 0.2 version? I'm finding it hard to believe that this hasn't been fixed in the binary packages yet!

Revision history for this message
Charlie Figura (cfigura) wrote :

Whups! I'm running gutsy, not feisty.

Revision history for this message
Charlie Figura (cfigura) wrote :

Cancel this. The problem is different - knetwork manager thinks that the LEAP network I'm trying to connect to is WEP.

Changed in knetworkmanager (Suse):
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.