This would be handy, especially when companies develop a VPN solution, and want to distribute client VPN profiles, like openvpn. the user receives a bundle via USB in the security office containing that user's
cert/key. If one could develop the working profile, export in some editable format, batch edit - could be really efficient. On 31.05.2017 16:25, Alex Ferm wrote: > > It is my experience that the easiest way to "backup" a connection is > just to copy its keyfile. I work exclusively with system connections, > so that may not be as easy with user connections. It also appears that > nmcli has import/export support for VPN connections. If VPN > connections are all you care about, you could probably get away with a > simple bash script that finds and exports VPN connections and a > similar script to re-import them on the destination host. > > > On 05/31/2017 07:45 AM, Greg Oliver wrote: >> I have emailed a couple times about backing up connections since I >> have close to 100 VPNs I would like to restore when I upgrade my OS. >> The dconf/gconf methods from the past are no longer valid. >> >> I am willing to put in the work (since it is an obvious pain to do 2x >> a year when I upgrade) to write (I know python, perl and all shells) >> scripts to backup/restore connections. I see there are python >> bindings, but there are also a lot of unknowns (user or system >> connections, etc..). >> >> Is this something that would gain traction, or is it always going to >> be a moving target? I assume python bindings would not change (much >> like the kernel ABIs), but I obviously do not know. >> >> In the past I have used dconf, but the connections are no longer >> stored there, so you see my dilemma. >> >> If this sounds like something the network manager devs are interested >> in, let me know - otherwise I will figure out how to roll my own. It >> is an unusual use case I know, but I work with our clients through >> VPN connections all day every day, so it would save me quite a bit of >> time to be able to carry them over from upgrade to upgrade, etc.. >> >> If this does not seem like something important, I will just do >> something local. TIA! >> >> >> >> Thanks >> >> -Greg >> >> >> _______________________________________________ >> networkmanager-list mailing list >> [email protected] >> https://mail.gnome.org/mailman/listinfo/networkmanager-list > > -- > Alex Ferm > PetroPower, LLC. > 3003 E. 37th Street N. > Suite 100 > Wichita, KS 67219 > > > _______________________________________________ > networkmanager-list mailing list > [email protected] > https://mail.gnome.org/mailman/listinfo/networkmanager-list
_______________________________________________ networkmanager-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/networkmanager-list
