bootgrid: clean up converter compatibility code
Only other consumer is Nginx in plugins, but worst case scenario
these timestamps will render as... timestamps, which in that form
are sortable anyway. It's likely this was throwing an error anyway
The "sorters" weren't actually accounted for in the compat
translation, so this wasn't overridable. Fix this here.
interfaces: follow up on DHCP option sanitization
@sopex noted a) that two semicolons were missing which were likely
lost to a refactoring step and b) allowing "medi;a" to avoid the
sanity scan for option modifiers. To fix that second part we use
the normalization of interfaces_dhcp_safe() directly before returning
the parsed arguments to the caller. That way the result is clear
and easy to check.
PR: GHSA-5rx3-w735-74wm
(cherry picked from commit 9e7fad6c3188e148f5066e948cebba19f8682765)
interfaces: follow up on DHCP option sanitization
@sopex noted a) that two semicolons were missing which were likely
lost to a refactoring step and b) allowing "medi;a" to avoid the
sanity scan for option modifiers. To fix that second part we use
the normalization of interfaces_dhcp_safe() directly before returning
the parsed arguments to the caller. That way the result is clear
and easy to check.
PR: GHSA-5rx3-w735-74wm
Services: Kea DHCPv4/6: Add decline_probation_period and set lower default to mitigate faulty client implementations to consume the whole pool (#10294)
* Services: Kea DHCPv4/6: Add decline_probation_period and set lower default to mitigate faulty client implementations to consume the whole pool.
* Use isSet() since 0 is allowed
Services: Kea DHCPv4/6: Some cleanup regarding isEmpty) usage when 0 is allowed in IntegerFields, and ensure no IntegerField accepts negative values. (#10295)
Services: Kea DHCPv4/6: Add decline_probation_period and set lower default (KEA sets 1 day) to mitigate faulty client implementations to consume the whole pool.
