Hi, > If I distribute my VPN client as a Zip file then what ever name I give the > VPN config file, I will obviously make the batch file the same. > * provider.ovpn > * provider_up.bat > This is certainly not a difficult hurdle to side-step. > > > > It's easy for an unsuspecting user to "import" a config file downloaded > > from somewhere, but to get the batch file into the right location they > > have to deliberately copy it there. One can say that we treat that > > action as equivalent to "--script-security 2". > > See Zip above.. > Unsuspecting users is exactly who I thought the OpenVPN wanted to protect.
What I meant was the import menu in the GUI will not import a zip file, only the .ovpn. When we add a smarter import option we'll have to warn the user about such scripts. Also, I'm all for patches to improve --script-security handling as well as for controlling scripts run by the GUI. I had tried but found it to be beyond my foo to come with a decent way to do this. Selva _______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
