Re:BPF port-based firewall for systemd services
by jdc on Friday August 30, 2019 @01:13PM
(#20840485)
I'm thoroughly skeptical that general acceptance means that JIT compilation doesn't increase the attack surface of the stack.
Re:BPF port-based firewall for systemd services
by Dylan16807 on Friday August 30, 2019 @06:18PM
(#20843224)
You'd need an interpreter at least, to avoid some kind of hideously complex system.
So it's a question of interpreter vs. JIT, and a JIT makes it more feasible to use an ultra-simple language with aggressive verification, without losing too much speed.
Every feature has an attack surface, but you have to compare against the alternative, not the lack of feature.
(This assumes that you can't force it to use a kernel interpreter despite the JIT existing. Otherwise perhaps that is the part that should be disabled.)
Re:BPF port-based firewall for systemd services
by ignoramous on Friday August 30, 2019 @02:57PM
(#20841510)
Tangential: Does your team publish papers or write blog posts on the kind of engineering or research it does? I'd like to read it, or at least add it to my queue. Thanks.
Re:BPF port-based firewall for systemd services
by jauer on Friday August 30, 2019 @10:43PM
(#20844341)
There was a recent talk on tupperware that gets into some of what Alex's team does: https://engineering.fb.com/data-center-engineering/tupperwar...
Re:BPF port-based firewall for systemd services
by ignoramous on Saturday August 31, 2019 @07:08AM
(#20845628)
That was interesting. Thanks.
Second, I don't actually agree. JIT compilation is a generally accepted approach -- who cares what the IR is? And the bpf runtime is ULTRA constrained, so you can't slip a `system("rm -rf /")` in there (by a long shot).
[0] https://www.kernel.org/doc/html/latest/bpf/btf.html