aboutsummaryrefslogtreecommitdiffstats
path: root/config/openvpn-client-export/openvpn-client-export.inc
Commit message (Collapse)AuthorAgeFilesLines
* Update OpenVPN Client Export with OpenVPN 2.3.6 installers.jim-p2014-12-011-2/+5
|
* Update OpenVPN installers to 2.3.5-Ix01. Add -I6xx installers.jim-p2014-11-041-7/+17
|
* Don't add a second tls-auth line when exporting for Viscosity.jim-p2014-04-241-1/+1
|
* Fix various OpenVPN Client Export protocol issues that prevented the export ↵jim-p2014-04-241-5/+18
| | | | from generating a valid IPv6 endpoint client config; Also the Windows installer files have been bumped to 2.3.3-I002
* Avoid a PHP error in OpenVPN client export if the user chooses one of the ↵jim-p2014-04-241-0/+3
| | | | automatic port forward methods but has no port forwards defined.
* fix typoChris Buechler2014-04-231-1/+1
|
* fix Viscosity OpenVPN client export with advanced optionsChris Buechler2014-04-161-1/+1
|
* Instruct the client to use a random local port for OpenVPN in the exported ↵jim-p2013-11-251-5/+11
| | | | configuration.
* Bring back tls-remote as a non-default option for those stuck on older ↵jim-p2013-11-131-8/+20
| | | | clients. Also give the user the option to disable server cert CN verification. Implements #3318
* OpenVPN Client Export - Update OpenVPN installers to 2.3.2-I003. Fix 64-bit ↵jim-p2013-11-131-3/+3
| | | | postinstall script, enable 64-bit export. (Note: 64-bit export does not work with OpenVPNManager)
* Don't include a pkcs12 line in the Viscosity config, it uses individual ↵jim-p2013-11-121-1/+1
| | | | ca/cert/key lines and not pkcs12.
* Disable "verify-x509-name" in some cases. It can cause problems with ↵jim-p2013-11-111-1/+3
| | | | auth-only setups, and also with Yealink/Snom phones since they are stuck on an older OpenVPN version that does not support this feature.
* Allow the client export package to properly match the compression setting on 2.2jim-p2013-10-311-2/+8
|
* tls-remote is deprecated, use verify-x509-name, which also works on the iOS ↵jim-p2013-10-311-2/+2
| | | | client so no need to exclude it from getting the line either.
* Add auth line to client config if configured on the server (drop-down is ↵jim-p2013-10-311-0/+4
| | | | there to set it in master/2.2)
* Add an "Automatic" multi-wan option to the client export package that will ↵jim-p2013-10-231-20/+113
| | | | look for and use port forwards targeting this instance rather than the IP directly. This way you can bind to LAN or localhost, port forward on all WANs to the LAN IP:port, and then the export will include remote lines for every port forward it finds. Also works to forward multiple ports at the same instance.
* Use OpenVPN Manager client management port if specified for the server concernedPhil Davis2013-08-251-2/+7
| | | | | | If the OpenVPN server has the client management port field specified, then use that port number when generating the OpenVPN Manager client config file, otherwise use the default of "166". See: forum.pfsense.org/index.php/topic,63668.0.html Discussion: https://github.com/jochenwierum/openvpn-manager/issues/17 Related pull request on pfsense repo: https://github.com/pfsense/pfsense/pull/783
* Replace spaces in a CN with _ in filenames when exporting an OpenVPN client. ↵jim-p2013-07-141-2/+2
| | | | Also only use a CN if there isn't a username to use instead. Unbreaks Windows Installer export with spaces in CN.
* Properly handle filenames containing spaces when exporting an archive. Fixes ↵jim-p2013-07-111-4/+8
| | | | #2856
* When we don't need a client cert, add a line to tell the client that we ↵jim-p2013-07-111-0/+3
| | | | don't need a client cert, or else the OpenVPN Connect app will try to force the user to pick one.
* Add Proxy Type OptionN0YB2013-06-061-10/+12
| | | | Allow UPD protocol with socks proxy
* Add Proxy Type OptionN0YB2013-06-051-2/+8
|
* Do not mix OpenVPN's secure modesbcyrill2013-01-271-1/+1
|
* Update OpenVPN Client Export again, rearrange options to make them more ↵jim-p2013-01-221-18/+25
| | | | clear/easy to follow. Also bump version and promote package status to reflect how stable it has become.
* Fix up the inline config format a little to make Android and iOS both happy.jim-p2013-01-171-16/+10
|
* Merge pull request #339 from PiBa-NL/openvpn-client-export-certchecksJim P2012-11-241-13/+22
|\ | | | | openvpn-client-export, better error reporting on unsupported OpenVPN configurations
| * removed purpose checking because: "Certs created before 2.0.1 can have the ↵PiBa-NL2012-11-241-6/+0
| | | | | | | | "wrong" purpose but we should not invalidate them."
| * openvpn-client-export, better checking/error reporting on ↵PiBa-NL2012-11-241-13/+28
| | | | | | | | unsupported/illogical OpenVPN configurations
* | openvpn-client-export, use certificate common-name in the exported files ↵PiBa-NL2012-11-241-6/+5
| | | | | | | | filenames.
* | openvpn-client-export, use certificate common-name in the exported files ↵PiBa-NL2012-11-211-5/+7
|/ | | | filenames.
* openvpn-client-export, added option to include OpenVPNManager in windows ↵PiBa-NL2012-11-051-18/+51
| | | | setup, this solves the issues with Windows7/Vista client machines where elevated permissions are required by running OpenVPN as a service.
* Write client install exe to temp dirPhil Davis2012-10-031-4/+4
| | | The code did not work on nanobsd, due to $workdir templates being on a read-only mount point. The appropriate $client_install_exe needs to be written straight to $tempdir rather than first done in $workdir templates. And also we don't want to be writing to $workdir templates every time we make a client install package for someone.
* Add export option for OpenVPN 2.3 beta client as well as the existing one.jim-p2012-10-021-2/+15
|
* Make quoting the server CN optional since it seems to break more clients ↵jim-p2012-09-181-7/+16
| | | | than it fixes; Add a third Yealink variant.
* Enclose this in quotes, since it may contain spaces. Otherwise, openvpn will ↵jim-p2012-08-091-1/+1
| | | | choke on it.
* Fix inline client exportjim-p2012-08-091-0/+2
|
* Update config/openvpn-client-export/openvpn-client-export.incdhatz2012-08-091-1/+1
|
* Teach the OpenVPN Client Export package how to make config archives for ↵jim-p2012-08-031-0/+73
| | | | Yealink T28, Yealink T38g, and SNOM SIP handsets.
* Add inline config format that the openvpn client for android likes (ca, ↵jim-p2012-07-011-40/+65
| | | | cert, key, tls-auth inside single config file) to the export package.
* Generalize this variable namejim-p2012-06-301-4/+4
|
* Move this common code into a function.jim-p2012-06-301-86/+25
|
* client export code cleanup. Remove a bunch of redundant/duplicate code.jim-p2012-06-301-1/+1
|
* Fix braces around variable - Fixes #2429jim-p2012-05-141-1/+1
|
* The client export was missing a newline after the ns-cert-type which would ↵Leroux Cifer2012-05-021-1/+1
| | | | thus mess up comp-lzo and such afterwards.
* Fix syntax errorjim-p2012-04-041-2/+2
|
* Handle a blank hostname a bit more gracefully when exporting OpenVPN.jim-p2012-04-041-3/+5
|
* Add contributed patch to optionally encrypt the key for Viscosity bundles. ↵jim-p2011-11-291-2/+13
| | | | Fixes #2032
* If we can determine that the server cert has nsCertType=server, then add ↵jim-p2011-11-221-0/+9
| | | | ns-cert-type server to the client config.
* Fix up various export scenarios that were not functioning properly.jim-p2011-11-171-5/+18
|
* Correct path to binaryScott Ullrich2011-11-021-1/+4
|