News for hackers. Stuff that matters.
Re:BPF for Hid Drivers by anonymousiam on Wednesday November 16, 2022 @12:12PM (#33626678)
Doesn't this "solution" just move the problem? I suppose if it's easier to write/update/maintain a set of eBPF rules for quirky HIDs than it is to update the drivers/modules, then this is an improvement.

I wonder how Linus feels about this? Does it introduce a new attack surface for malware injection?

Re:BPF for Hid Drivers by tenebrisalietum on Wednesday November 16, 2022 @12:26PM (#33626880)
Root adding eBPF code is not worse than root being able to `insmod` a kernel module.
Re:BPF for Hid Drivers by akira2501 on Wednesday November 16, 2022 @01:40PM (#33628252)
It adds a layer where complex attacks can hide. I'm not so much worried about the 'insmod' as I am about long term data exfiltration being used against me. This certainly does seem to make that a little easier.
Re:BPF for Hid Drivers by ecnahc515 on Wednesday November 16, 2022 @05:13PM (#33631595)
A kernel module could exfiltrate data just as easily though.
Re:BPF for Hid Drivers by egberts1 on Thursday November 17, 2022 @11:56AM (#33641787)
Wrong, eBPF is way, way worse.

At the very least, Linux kernel has signed driver modules.

Re:BPF for Hid Drivers by mdaverde on Thursday November 17, 2022 @03:48PM (#33645439)
Can you explain why you consider it to be worse?

eBPF is also working on signed programs [0]

[0] https://lwn.net/Articles/853489/

Re:BPF for Hid Drivers by egberts1 on Thursday November 17, 2022 @06:58PM (#33647794)
eBPF has a way to go before it is secured enough.

One should not use eBPF in production machines (along with many other things that uses the mixed write-execute memory regions such as web browsers with JavaScript enabled).

Re:BPF for Hid Drivers by tinus_hn on Thursday November 17, 2022 @07:13AM (#33637865)
This solution is like using Javascript instead of C. You can’t write a buffer overflow in Javascript, and you can even sandbox it. That way you can allow code to run that has had less review.