4 ms·
Actually we spent MONTHS debating the pros and cons of adding a sudo on Windows. Curiously, Windows is more secure than linux because it _doesn't_ have a sudo.
by zadjii 7y ago
Actually we spent MONTHS debating the pros and cons of adding a sudo on Windows.
Curiously, Windows is more secure than linux because it _doesn't_ have a sudo.
In Windows, any application can set messages to another window at the same integrity level with SendMessage/PostMessage.
If you had a `sudo` on windows, you could have a medium-IL terminal window which is talking to a high-IL process (running with the hypothetical sudo), and any other medium-il process could drive the console, effectively creating an escalation of privilege attack vector.
Its very much by design.
- majkinetor 7y agoThere are solutions to that, like IPC with some systemic "sudo server". > Curiously, Windows is more secure than linux because it _doesn't_ have a sudo. Seriously, even if so, and I really much doubt it couldn't be fixed, its case where too much security is bad for your choices. Majority of Windows devs disable UAC, honestly. Like, almost all of them ? Because its unusable and that Windows sudoers file variant named compatibility something something is just unusable too. I keep telling my 100+ IT guys (mostly devs), do not disable UAC, its good to know that something requires elevation (even tho it sucks but there are bearable powershell sudo scripts) and you will certainly have to make it on the build server later anyway. But they hate it with passion. I learned to accept the terror. There are horde of people asking questions on how to disable startup UAC screen for many tools (one example: everything search engine). What I do now is use task scheduler (like many others) to overcome it.