<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/interface-definitions/include/firewall/packet-length.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-03-06T19:15:15+00:00</updated>
<entry>
<title>T5055: Firewall: add packet-type matcher in firewall and route policy</title>
<updated>2023-03-06T19:15:15+00:00</updated>
<author>
<name>Nicolas Fort</name>
<email>nicolasfort1988@gmail.com</email>
</author>
<published>2023-03-06T18:30:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=16c494c2f1364283988b52e35faf6b01745bbed4'/>
<id>urn:sha1:16c494c2f1364283988b52e35faf6b01745bbed4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>xml: T4698: validating a range must be explicitly enabled in the validator</title>
<updated>2022-09-22T17:44:50+00:00</updated>
<author>
<name>Christian Poessinger</name>
<email>christian@poessinger.com</email>
</author>
<published>2022-09-22T17:38:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=e1d3fd0b29a1178e775cbc86f6c0011a682506ba'/>
<id>urn:sha1:e1d3fd0b29a1178e775cbc86f6c0011a682506ba</id>
<content type='text'>
This extends commit 28573ffe4f ("xml: T4698: drop validator name="range" and
replace it with numeric"). The first version allowed both a range and discrete
numbers to be validated by the numeric validator.

This had a flaw as both 22 and 22-30 were valid at the same time. The generic
"port-number.xml.i" building block only allows a discrete number. Now if a user
set port 22-30 for e.g. SSH the daemon did no longer start. This is why range
validation must be explicitly enabled.
</content>
</entry>
<entry>
<title>xml: T4698: drop validator name="range" and replace it with numeric</title>
<updated>2022-09-16T07:16:17+00:00</updated>
<author>
<name>Christian Poessinger</name>
<email>christian@poessinger.com</email>
</author>
<published>2022-09-16T07:15:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=28573ffe4fd939a266006840f999c99babe89dce'/>
<id>urn:sha1:28573ffe4fd939a266006840f999c99babe89dce</id>
<content type='text'>
After T4669 added support for range validation to the OCaml validator there is
no need to keep the slow Python validator in place.

Raplace all occurances of &lt;validator name="range" argument="--min=1 --max=65535"/&gt;
with &lt;validator name="numeric" argument="--range 1-65535"/&gt;.
</content>
</entry>
<entry>
<title>firewall: T4651: re-implement packet-length CLI option to use &lt;multi/&gt;</title>
<updated>2022-09-03T18:37:10+00:00</updated>
<author>
<name>Christian Poessinger</name>
<email>christian@poessinger.com</email>
</author>
<published>2022-09-03T18:37:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=d9eb48a0ced1eb60bd00fe2f18559b3c780ee98a'/>
<id>urn:sha1:d9eb48a0ced1eb60bd00fe2f18559b3c780ee98a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Firewall: T4651: Change proposed cli from ip-length to packet-length</title>
<updated>2022-09-01T19:08:37+00:00</updated>
<author>
<name>Nicolas Fort</name>
<email>nicolasfort1988@gmail.com</email>
</author>
<published>2022-09-01T19:08:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=312ee15058fbb26feb6a93520417f0d5343ad15b'/>
<id>urn:sha1:312ee15058fbb26feb6a93520417f0d5343ad15b</id>
<content type='text'>
</content>
</entry>
</feed>
