Bug 227418 - knetworkmanager (vpnc) does not ask for password when Always Ask is set
Summary: knetworkmanager (vpnc) does not ask for password when Always Ask is set
Status: RESOLVED DUPLICATE of bug 244416
Alias: None
Product: knetworkmanager
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Mandriva RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Will Stephenson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-17 19:49 UTC by Andrey Borzenkov
Modified: 2011-02-07 03:49 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey Borzenkov 2010-02-17 19:49:01 UTC 
Version:            (using KDE 4.4.0)
OS:                Linux
Installed from:    Mandriva RPMs

My VPNC gateway is using one time password so I cannot store user password permanently in connection settings and have to enter it every time. I created VPNC connection using knetworkmanager but it never asks for password; of course connection attempt always fails.
Comment 1 Michal Hlavinka 2010-04-16 10:34:23 UTC 
I can see the same problem in kde 4.4.2 using knetworkmanager-0.9-0.17.20100310.fc13.x86_64

After I set up vpnc and click on it in the knetworkmanager menu nothing happens. Nothing at all, not even asked for password. I left user passphrase "always ask" because our vpn uses rsa token generated passwords changing every minute, so it's not possible to store that password
Comment 2 Rex Dieter 2010-06-08 19:04:30 UTC 
we've 2 independent confirmations @ redhat
Comment 3 Andrey Borzenkov 2010-07-18 18:15:55 UTC 
Suggested patch in bug 244416.

The reason it happens - VPN layer in knetworkmanager always saves secrets in kwallet; for secret with ALWAYS_ASK property it saves empty value. On connection it checks only whether *anything* was saved in kwallet, not whether individual secrets do have values.
Comment 4 Lamarque V. Souza 2011-02-07 03:49:13 UTC 

*** This bug has been marked as a duplicate of bug 244416 ***