Comment 19 for bug 262191

Yes, it's a first take on exactly what Dan Williams suggested: password types in the configuration dialog, and then saving passwords depending on that. I've added something so that as long as it's not a "rekey" or "reprompt" for the passwords, then it only asks for what's necessary.

Take this use case: I'm connecting to my work network, which requires a static group password, which i generally want to save in the keyring, and a dynamic, always-changing user password (SecurID). I set the group password to use "Default", the user password to "OTP" in the configuration dialog (same place as for the gateway and all of that stuff), then save. network-manager should only ask for the securid passcode, the auth-dialog has been modified so that only the user password, in that case, is asked for. Same could apply if the group password was dynamic, or if both passwords were.

Anyway, I'm not saying that this is the way to go, it's just a suggestion I brought up upstream. I think the best course of action currently should be to just patch network-manager-vpnc so that it's at the point where it was in Hardy, and then when and IF the other patch is accepted upstream, then we could integrate it (Jaunty or later).

Of course, another option would be, given enough outside testing, to directly integrate the password types patch in Jaunty Jackalope, and that will bring in an additional case to have the patch accepted upstream (I guess) but that's really not my call; I'm not the upstream maintainer, or the Ubuntu package maintainer, and not even MOTU. Hence why Ubuntu-Universe-Sponsors are subscribed, and we'd be theoretically waiting for Alexander Sack or Soren Hansen's input (and possible code review) before the initial, regression-fixing patch can be applied to the network-manager-vpnc package.