[OpenVPN home] [Date Prev] [Date Index] [Date Next]
[OpenVPN mailing lists] [Thread Prev] [Thread Index] [Thread Next]
Google
 
Web openvpn.net

[Openvpn-users] Configurable Installer


  • Subject: [Openvpn-users] Configurable Installer
  • From: "Bert Shuler" <bshuler@xxxxxxxxxxxxxxxxxxx>
  • Date: Tue, 16 Sep 2003 09:07:05 -0700

It would be most useful for the windows installer to be configurable,
meaning that when the user receives the install, it is pre-configured to
install and configure itself with the necessary parameters to connect to
a particular network. Also, we are currently using a number of different
files to configure each device. It might be helpful to have a standard
for packaging all configuration options into one file. I would suggest
something like the below:

a gzip compressed tar
naming format could be: [devicename].ovpnZ
where the [devicename] is replaced with the actual intended device name
(e.g.. MyCompany.ovpnZ)
inside the tar would be a config file named either [devicename].ovpn or
configuration.ovpn
also inside the tar would be all other files referenced in the .ovpn
file

additionally, I suggest that --config [devicename].ovpnZ would be a
intuitive way of using the .ovpnZ file and storing the .ovpnZ file in
the config directory should have the expected behavior for the windows
nt service.

A helper application that would open a simple installation wizard when
the execution of an .ovpnZ file was attempted would round out an
interesting way of automating openvpn configuration. Tasks that the
helper application would need to perform would be:

optionally reading a install.inf file located in the .ovpnZ file that
would allow for a zero user intervention install (other than a user
confirmation message and maybe a GNU license agreement.)
move the .ovpnZ file to the standard place where .ovpnZ files are
stored.
deal with collisions by either enumerating the device name in both the
.opvnZ and the enclosed .ovpn file names or optionally replace the
original with the new.
ask for and use if necessary a username and password that should be used
to elevate permissions
add devices
add/change client firewall rules
bring up the vpn connection
report success/failure to user and/or vpn administrator via email and/or
http post (should include installation logs)

Any comments/suggestion are welcome.

____________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users