GNOME Bugzilla – Bug 682575
cannot store vpnc passwords in config file
Last modified: 2020-11-12 14:25:52 UTC
networkmanager-vpnc is insisting on storing the xauth password and ipsec secret it my gnome keyring. I tried manually placing them in the conf file under /etc/NetworkManager/system-connections but they are ignored. Last I remembered (a year or so) this was possible.
For whatever reason, the vpnc plugin decided to store my Xauth password in the config file, and from this I was able to figure the rest out. [vpn] xauth-password-type=save Xauth password-flags=0 ipsec-secret-type=save IPSec secret-flags=0 [vpn-secrets] Xauth password=XXX IPSec secret=XXX This is not obvious at all. If it's a connection that's available to all users, why does NM even try to use my personal keyring?
(In reply to comment #1) > This is not obvious at all. If it's a connection that's available to all users, > why does NM even try to use my personal keyring? The expectation with connection types that have a username is that if it's "available to all users", that means that all users can use it, but each user will have their own username and password. Anyway, this might be fixed now... Jirka, did your password-saving changes affect VPNs too?
bugzilla.gnome.org is being shut down in favor of a GitLab instance. We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time. If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/ Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).