News for hackers. Stuff that matters.
Re:OpenBSD was right to disable hyperthreading [video] by moviuro on Tuesday September 03, 2019 @10:11AM (#20866614)
> setting it up to be conservative just like OpenBSD

Meh. Probably for superficial stuff, yes. But would Linux kill cat(1) if it did some network calls? I bet not. See https://www.openbsd.org/innovations.html

Re:OpenBSD was right to disable hyperthreading [video] by roryrjb on Tuesday September 03, 2019 @10:23AM (#20866716)
You can do this with seccomp, but of course not by default like pledge and OpenBSD.
Re:OpenBSD was right to disable hyperthreading [video] by ailideex on Tuesday September 03, 2019 @10:23AM (#20866720)
You could block it's network access with network namespaces: http://man7.org/linux/man-pages/man1/unshare.1.html

I'm sure you could engineering something to kill it also with currently kernel functionality - though I would need to do more research to say what.

Re:OpenBSD was right to disable hyperthreading [video] by majewsky on Tuesday September 03, 2019 @11:04AM (#20867170)
BPF can filter syscalls.
Re:OpenBSD was right to disable hyperthreading [video] by pas on Monday September 09, 2019 @10:24AM (#20918466)
AppArmor does that. I don't know what's the default profile for cat, but a simple one line "deny network;" works. It's up to the distribution.