So, other than validation or something... Which, if you are already parsing the file into json and back again... Means you already can parse pf.conf files, and just do validation directly there.
So if it's just backing up, then yeah why add the extra step of converting the file before backing it up
JSON is generally a pretty poor configuration language, so I wouldn't hope that it would be adopted.
I suspect that the purpose of this is to be able to ingest pf.conf files into a larger security tool. Something like an NDR/XDR/SOAR, or perhaps Splunk.
SecOps wants to know what the existing policies are (for compliance and validation), and to orchestrate enforcement when an IoC (or whatever) prompts investigation and action. Getting the format into JSON opens up the whole landscape for integration into existing tooling.
djoldman•4mo ago
hnlmorg•4mo ago
baranul•3mo ago
[1]: https://www.youtube.com/watch?v=MvFHT0N9inw (Just Try Out New Languages - part of a longer interview)
[2]: https://news.ycombinator.com/item?id=43462676 (TUI editor and Vim/Neovim alternative)
[3]: https://github.com/vlang/awesome-v
SoftTalker•4mo ago