On 2024/12/26 10:35, William Rusnack wrote: > > Synopsis: iked.conf(5) incompletely documents comment syntax and has > > potentially problematic behavior where comments can be continued with line > > continuations (\), leading to unexpected configuration parsing. Man page > > also fails to document that comments can have preceding whitespace and > > appear at end of lines. > > Category: bin > > Description: > The iked.conf(5) man page currently states: > > Lines beginning with ‘#’ and empty lines are regarded as comments, > and ignored. Lines may be split using the ‘\’ character. > > However, the parser actually allows for > - comments to be continued with line continuations `\\\n` (Possibly a > bug) > - preceding white space > - trailing comments > > # Comments Continued with Line Continuations (Possible Bug)
This is common to many parse.y-based config parsers in OpenBSD which are kept in sync. Changing some of those from the current behaviour will result in different parsing of config files, resulting in possibly *quite bad* different behaviour in some, especially in pf.conf.
