Ted Unangst wrote:
> I think not. If you intentionally store binary data in syslog (why?) you can
> use
> base64. The vis call is to prevent harm, not guarantee it's unambiguous.
> Lots of potential syslog calls are already ambiguous if the user provides
> inputs containing spaces. A structured
On 2022-06-02, Theo de Raadt wrote:
But please consider this impact of the change you propose.
>
> There is one additional flag, VIS_NOSLASH, which inhibits the doubling of
> backslashes and the backslash before the default format (that is, control
> characters are represented by `
On Fri, Jun 03, 2022 at 03:33:57PM +0200, Claudio Jeker wrote:
> fib_priority was slapped into the code by passing it around all the time.
> It is much smarter to use a global value in kr_state for the fib_prio and
> then tag F_BGP_INSERTED routes with RTP_MINE (0xff) which is an impossible
> RTP v
fib_priority was slapped into the code by passing it around all the time.
It is much smarter to use a global value in kr_state for the fib_prio and
then tag F_BGP_INSERTED routes with RTP_MINE (0xff) which is an impossible
RTP value. With that changing the prio requires "only" a fib decouple,
chang
