Bug 232425 - Always Allow does not seem to work for KNetworkManager and others
Summary: Always Allow does not seem to work for KNetworkManager and others
Status: RESOLVED NOT A BUG
Alias: None
Product: kwalletmanager
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Michael Leupold
URL:
Keywords: reproducible, usability
Depends on:
Blocks:
 
Reported: 2010-03-28 05:19 UTC by Vishal Rao
Modified: 2010-03-28 14:41 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vishal Rao 2010-03-28 05:19:03 UTC
Version:            (using KDE 4.4.1)
OS:                Linux
Installed from:    Ubuntu Packages

Using Kubuntu 10.04 development version with the latest updates for 4.4.1 with 4.4.2 just around the corner.

While logging in KWalletManager prompts for password (for enabling WPA2 protected Wifi connection) everytime even though the "Always Allow" option is selected for KNetworkManager.

I believe that other apps are similarly affected like Kopete and KmicroBlog but unsure of that...
Comment 1 Vishal Rao 2010-03-28 05:22:58 UTC
Please let me know if you would like me to test something, or provide additional details, or confirm whether this is just for KNetworkManager or other apps that depend on KWalletManager... (could just be KNetworkManager issue and not KWalletManager).
Comment 2 Michael Leupold 2010-03-28 08:31:57 UTC
Please check the following:

1. When KWallet prompts whether to allow access to the wallet inside the dialog it tells you about the name of the application (eg. "Application X wants to access the wallet"). Is that always the same when it prompts for KNetworkManager?

2. After clicking "Always Allow", please check inside KWallet's settings if KNetworkManager is added to the ACL (2nd tab).
Comment 3 Vishal Rao 2010-03-28 11:24:04 UTC
1. Yes, it is always showing "KNetworkManager" everytime it prompts to enter the wallet password.

2. Yes KNetworkManager is added to the ACL marked Always Allow. There is also "Network Management" entry there along with "Plasma Workspace".

I removed the microblog widget and also deleted the always-allow entries for both knetworkmanager and 'network management' and the behaviour is the same, ie, it keeps prompting for password as it did before and also does not again ask whether to always-allow or not... !

I have had this Kubuntu 10.04 development release for a few weeks now since alpha3, can this bug be investigated as is, or do I need to reinstall afresh (say when Beta2 is released maybe with KDE 4.4.2) to get a fresh look on this issue?
Comment 4 Michael Leupold 2010-03-28 12:01:54 UTC
I might have gotten you wrong on your question:
Are you (a) prompted for the wallet password or (b) whether you want to allow KNetworkManager to be able to access the wallet?

(a) Is how it's supposed to be as the wallet is stored encrypted with the password you set. The only way to currently get rid of this is using an empty password.

(b) Is what I initially understood. This would be a bug.
Comment 5 Vishal Rao 2010-03-28 12:25:15 UTC
a) Ah, changing to a blank password prevents the prompt. I now realise
it was just an initial prompt to open the wallet - just that
KNetworkmanager was asking first misled me.

b) Seems to be working as expected and not a bug.

I must have gotten mixed up due to GNOME keyring behaviour... will
have to check that out too how it seems to work (to allow wifi/wpa2
auto connect) even though I have set a password...

I guess this is an invalid bug I filed, should have just checked in
the forums sorry, go ahead and close... thanks!
Comment 6 Michael Leupold 2010-03-28 14:41:02 UTC
GNOME Keyring opens the login keyring which holds the WiFi password using a PAM module. I'm currently working on the same feature for KWallet but unfortunately it's not ready for release yet.