Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

“Be warned though, deleting the wrong thing can stop applications from working, or even break the entire operating system.“

You gotta love Windows.



Yes, because if I go to /etc or /var and delete some random thing, linux is just magical and nothing will possible break.

Cut the crap


No, you cut the crap.

/etc can be entirely readonly to most apps, many of them also either wont start from root or drop permissions right after loading.

That is not the case for registry, far more ways to fuck up.


To delete system-wide things in the registry you will be prompted to escalate to admin privilege. It's usually one click.

To delete things in /etc you will be asked to gain root privilege. It's usually one click (You might be asked to confirm your password).

Deleting things when admin/root can break things in both cases.

Let's just admit it and move on.


Hold on, You pivoting.

The paragraph you quoted is in context warning the user about MANUAL intervention in the registry, that requires privileged access. So we aren't comparing it to "what can random app do", but what can super user do.


Read my answer below


This is the same case in any OS when you're deleting things with root privileges.


I macOS you can’t delete system files, even with root privileges, unless you disable system integrity, which requires a restart.

Not the same at all.


in macOS a developer is like 90% likely to already have SIP disabled, because if at any point they had to do even one single thing that SIP didn't like, they would have had to completely turn off all security for the entire operating system


Where did you take that percentage from? It’s very likely the other way around. Almost no one, developers included, have SIP disabled.

If you need kernel extensions you should look for a different solution, at least on the Mac.


Little Snitch required a kernel extension until the Network Filter API was introduced. Homebrew required SIP to be disabled when it was first introduced but that's almost definitely fixed now. Some other software like certain hypervisors could have required it. I just think it's more likely for someone to disable SIP than find a different program that doesn't mind it, and those programs were all over the place when it was first introduced. Less so now, I suppose.

> If you need kernel extensions you should look for a different solution, at least on the Mac.

In 2023 sure.


Just because current OS suck at protecting themselves, that doesn't mean that it is acceptable.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: