361–370 of 439 posts
I already use https://github.com/lukesampson/psutils which has a sudo.ps1, which I install via scoop (I know that's a mouthful, but I just install scoop and run `scoop install sudo`). I used it from powershell literally just before I opened this article (after copy-pasting a password, I copy some random text laying around in the browser, like "com", then run `sudo restart-service -name 'cbdhsvc*'` to clear the clipbo…
Then Microsoft doubles down and introduces a better prompt called WSL - the Windows Subsystem for Linux because the Windows command prompt still sucks... and this is just a Ubuntu VM in Windows.
And now they implement Sudo?
Microsoft hasn't learned the first lesson of holes - when you find yourself in one, stop digging.
Earlier quoted context omitted.
Also known as, you don't know technically anything about Windows. There is a very big difference between supporting UNIX, and Linux kernel syscalls ABI on top of pico processes, the technology from Drawbridge kernel taken out from Microsoft Research, which incidentally is also used to port MS SQL Server into GNU/Linux.
who cares? they still abandoned it because it didn't work
As for the rest I could provide examples of how the BSDs and Solaris failed in similar attempts to clone Linux syscalls table, despite being UNIX, before Microsoft's attempt, but who cares?
Earlier quoted context omitted.
Why can't you do this with the tool that already exists to do the exact same thing, called runas?
A link in the article explains ... https://learn.microsoft.com/en-us/windows/sudo/#how-is-sudo-...
So Microsoft implicitly admits DOS sucks and creates a PowerShell prompt. Then Microsoft doubles down and introduces a better prompt called WSL - the Windows Subsystem for Linux because the Windows command prompt still sucks... and this is just a Ubuntu VM in Windows. And now they implement Sudo? Microsoft hasn't learned the first lesson of holes - when you find yourself in one, stop digging.
Yep, it's really happening. Sudo is coming to Windows. It's obviously not just a fork of the linux sudo - there's enough that's different about the permissions structure between OS's that just a straight port wouldn't make sense. But the dream of being able to run commands as admin, in the same terminal window - that's the experience we're finally bringing to users. I've been working on this for the last few months n…
The real question is, where will incidents be reported to if you're not in the sudoers file?
Earlier quoted context omitted.
In addition to not being a one-to-one port, Sudo for Windows is a completely unrelated command. > it does the same function which is to elevate a unprivileged command That's only one of the use cases of Sudo. Here's a description of Sudo from the official manual [1]: > sudo, sudoedit — execute a command as another user Sudo for Windows can't do that. It's mentioned in its FAQ: > the sudo command on Windows does not s…
> like a cat command that can't concatenate files Oh, that's a good counter-example to your own point: 99% of people who use cat don't care about this functionality.
I guess this is a thing on Windows now. However at the moment, it seems to be a very insecure thing. But hey it's early days... I predict they'll eventually get it right 125 patch Tuesdays from now. https://fosstodon.org/@serghei@mastodon.social/1119009868252...
MS in a nutshell:
Ready, fire, aim!
Users:
"Immediately, there was a problem."