<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/interface-definitions/include/openconnect-identity-based-config.xml.i, branch feature/T9082-codeql-cpp</title>
<subtitle>VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-1x.git/atom?h=feature%2FT9082-codeql-cpp</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-1x.git/atom?h=feature%2FT9082-codeql-cpp'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/'/>
<updated>2023-05-12T19:06:56+00:00</updated>
<entry>
<title>ocserv: T3896: improve XML definition and add warning about 3rd party configs</title>
<updated>2023-05-12T19:06:56+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2023-05-12T19:03:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=d1abba03229128c3f2a6f718e9f14f4d7285e74d'/>
<id>urn:sha1:d1abba03229128c3f2a6f718e9f14f4d7285e74d</id>
<content type='text'>
When enabling identity-based-config, users can add arbitrary config keys
that are processed by ocserv. The user "must know" what he is been doing, as
invalid config option will make the ocserv daemon go ... whoop!

Thus add a warning and inform the user about this setting.
</content>
</entry>
<entry>
<title>ocserv: T3896: refactor: change ocserv config-per-x node name</title>
<updated>2023-04-20T07:10:27+00:00</updated>
<author>
<name>Jamie Austin</name>
<email>jamiea@opusv.com.au</email>
</author>
<published>2023-04-20T07:07:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=93de3abe1368cab5ab8cd292689466d7af8e86bc'/>
<id>urn:sha1:93de3abe1368cab5ab8cd292689466d7af8e86bc</id>
<content type='text'>
Changes the node name from config-per-x to identity-based-config, as a result the j2 templates and vpn_openeconnect.py has been refactored to update the node name when accessing it's child nodes.
</content>
</entry>
</feed>
