> Can our installer use "custom locations", like "install all our software > to "d:\mystuff\openvpn\"?
Yes. > In that case, built-in paths won't work well (as was pointed out in the PR, > to my dismay). We could use something like C:\Windows\System32\SSL ? One could install Windows to a different drive, but the first line of defence could be a path defined by env variables. > > 2) use env variables for openvpn and openvpn-gui ? > > I think that this might be the most flexible and robust approach. On startup we could read the installation path from HKLM\SOFTWARE\OpenVPN and assume something like <installation-path>\ssl\openssl.cnf ? -- -Lev _______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
