vyos-1x.git/data/templates/openvpn/service-override.conf.tmpl, branch feature/T9082-codeql-cppVyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
https://git.amelek.net/vyos/vyos-1x.git/atom?h=feature%2FT9082-codeql-cpp2022-04-18T10:09:54+00:00openvpn: T4353: T4351: fix generation of openvpn-option string passed to daemon2022-04-18T10:09:54+00:00Christian Poessingerchristian@poessinger.com2022-04-18T10:09:54+00:00urn:sha1:f2b722a8879231383f8b0eaf92fda09eb121d78dopenvpn: T4333: migrate to new vyos_defined Jinja2 test2022-04-13T20:51:19+00:00Christian Poessingerchristian@poessinger.com2022-04-13T20:51:19+00:00urn:sha1:2b066e2cb8fe5340c3f32e4c29c75d4f3282363fOpenVPN: T3350: Changed custom options for OpenVPN processing2021-10-04T07:40:31+00:00zsdctaras@vyos.io2021-10-04T07:40:31+00:00urn:sha1:3fd2ff423b6c6e992b2ed531c7ba99fb9e1a2123
Custom OpenVPN options moved back to the command line from a
configuration file. This should keep full compatibility with the
`crux` branch, and allows to avoid mistakes with parsing options
that contain `--` in the middle.
The only smart part of this - handling a `push` option. Because
of internal changes in OpenVPN, previously it did not require an
argument in the double-quotes, but after version update in
`equuleus` and `sagitta` old syntax became invalid. So, all the
`push` options are processed to add quotes. The solution is still
not complete, because if a single config line contains `push` with
other options, it will not work, but it is better than nothing.