News for hackers. Stuff that matters.
Re:Why the CrowdStrike bug hit banks hard by jen20 on Wednesday July 31, 2024 @12:04PM (#41120397)
> With the current model kernel level access is required.

On Windows.

Re:Why the CrowdStrike bug hit banks hard by c0balt on Wednesday July 31, 2024 @12:12PM (#41120473)
Note: At least on Linux the main alternatives for this, either eBPF (e.g., pulsar or falcon) or a kernel module, both require this too.
Re:Why the CrowdStrike bug hit banks hard by kelnos on Wednesday July 31, 2024 @12:19PM (#41120545)
eBPF is at least somewhat sandboxed, no? So it doesn't quite have the access required to accidentally stomp on any portion of kernel memory it wants?
Re:Why the CrowdStrike bug hit banks hard by c0balt on Wednesday July 31, 2024 @12:25PM (#41120613)
Indeed it's executed via a Jit on something like a VM. However it can still, make your system quite disfunctional if, e.g., all filesystem or network calls are blocked.
Re:Why the CrowdStrike bug hit banks hard by vel0city on Wednesday July 31, 2024 @05:24PM (#41123619)
The version of the CrowdStrike sensor that caused kernel panics on RHEL/Rocky was using eBPF. It living in eBPF doesn't mean it can't cause system instability.

And as mentioned elsewhere, an eBPF module behaving badly but in valid ways can still make your system pretty unusable.

Re:Why the CrowdStrike bug hit banks hard by jen20 on Wednesday July 31, 2024 @09:35PM (#41125394)
macOS does not require this however.