Comment on Introducing Sudo for Windows
abbadon420@lemm.ee 10 months ago
It’s weird that its just “sudo” and not “Get-Admin-Acces”
It might just be an alias to a function similar to what you posted. Because like you can do curl but it really just calls invoke-webrequest, or ls for Get-ChildItem.
It is kind of weird that I took him this long to put this out though. I imagine a lot of people wrote their own version of this and it all probably very nearly the exact same.
Indeed. The name doesn’t follow the conventions of other commands in Windows/Powershell at all. And it is inconsistente too. “sudo” stands for “super user do”, but in Windows the notion of super user is called administrator. This will likely also cause confusion with people googling for “sudo” and getting to *nix related pages instead.
Nah, you can just google “windows+sudo” and look at if your results talk about unix or windows. And if they’re post 2024
rtxn@lemmy.world 10 months ago
No, it really is super simple, just:
Set-HostElevatedPrivilege -SubstituteUser Administrator -Privilege [Microsoft.Automation.HostPrivilege]::new("Administrators", $(hostname)) -Credential $(Get-Credential) -Command "ping 1.1.1.1"Aatube@kbin.social 10 months ago
It's more complicated than that. It seems to be able to configurably block user input for sudo'd commands, retain the existing environment, ditch it and open a new window, and remember that you've sudo'd in the last minute or so.