3 ms·
Out of interest, was this the project that eventually became wirefilter [1]? [1]: https://github.com/cloudflare/wirefilter https://github.com/cloudflare/wirefi
by SerCe 3y ago
Out of interest, was this the project that eventually became wirefilter [1]?
[1]: https://github.com/cloudflare/wirefilter https://github.com/cloudflare/wirefilter
- buro9 3y agoYup, that's the one. Uses wireshark display filters syntax to implement the ability to match traffic at any part of the stack. It's still used internally, but clearly they stopped updating the OSS version just after I left. They were updating things to make it fully compatible for everything owasp when I left which meant additions beyond the wireshark definition of display filters. Everything firewall and WAF was moving to the filters and also other traffic matching features too.
- SerCe 3y agoThank you for releasing it! I adopted wirefilter for a firewall rule testing project, firewalker [1]. But indeed, I wish Cloudflare kept maintaining its OSS version. [1]: https://github.com/SerCeMan/firewalker/ https://github.com/SerCeMan/firewalker/
- buro9 3y agoUnfortunately cloudflare has a poor OSS track record. Either not maintaining the public version, or promising to open things that then don't see the light of day (quicksilver database and replication, and their Rust reverse proxy and nginx/lua replacement - both of which were announced but never released). Most of what is OSS at cloudflare came in from elsewhere (V8) or was needed for collaboration (IETF), rather than started at cloudflare and opened.