Google must believe eBPF is mature enough (although they’ve been wrong before, see the Bluetooth stack rewrites and reverts in Chrome OS)
Note that desktop Linux distributions are working towards replacing iptables with nftables (added in kernel 3.13), so it seems as though there is some/broad consensus that we can do better than iptables these days
there is some/broad consensus that we can do better than iptables these days
oh yeah i have no doubt about that. just wondering what a healthy timeline looks like for the transition.
i don’t follow it especially closely, but had the impression bpf is still in the maturing phase regarding vulnerabilities. hopefully that is at least in part a sign it is being actively inspected and hardened with this purpose in mind - and i’m sure iptables still has many lurking vulns.
in summary, agree some form of transition is likely inevitable. wondering what the timeline will look like.
Google must believe eBPF is mature enough (although they’ve been wrong before, see the Bluetooth stack rewrites and reverts in Chrome OS)
Note that desktop Linux distributions are working towards replacing iptables with nftables (added in kernel 3.13), so it seems as though there is some/broad consensus that we can do better than iptables these days
oh yeah i have no doubt about that. just wondering what a healthy timeline looks like for the transition.
i don’t follow it especially closely, but had the impression bpf is still in the maturing phase regarding vulnerabilities. hopefully that is at least in part a sign it is being actively inspected and hardened with this purpose in mind - and i’m sure iptables still has many lurking vulns.
in summary, agree some form of transition is likely inevitable. wondering what the timeline will look like.