3 ms·
So the kernel should change and world should compromise security because a few people can’t figure out how to change defaults? I think there’s a few other secu
by hsbauauvhabzb 4y ago
So the kernel should change and world should compromise security because a few people can’t figure out how to change defaults?
I think there’s a few other security gaps, like pre-service start socket locking etc that you also haven’t considered.
- acdha 4y agoIt’s more that we should get rid of things which add risk and don’t offer much security and focus on getting people to use the real security measures. I’m still seeing vendors claim they have to run Java as root on Linux because it needs to bind on port 80/443 and it’d be nice to stop having to haggle.
- hsbauauvhabzb 4y agoYeah. Active directory is broken and has been for 25 years so that won’t be fixed. As strange as it sounds, aside from external implications (e.g. smb), a Java web service running as root _shouldnt_ have much impact - if you drop a shell on the host, it shouldn’t be doing anything more than running that one app. So dropping to jboss user or whatever should have no real world impact for low / sophistication attacks, as irrespective of user they’re still going to have access to db credentials etc. There are hypervisor breakouts etc which may be possible if you are root but not std user, but if you’re able to break out of hypervisors via 0day you probably also have privesc 0day. Edit: I say ‘shouldn’t matter’. If it does matter, you’ve probably got architectural issues in system design.
- acdha 4y agoWhen you say it doesn’t matter, consider how the attacker getting root improves their ability to persist, hide evidence, or prevent forensics.