- cross-posted to:
- technology@beehaw.org
- cross-posted to:
- technology@beehaw.org
You must log in or register to comment.
It’s weird that its just “sudo” and not “Get-Admin-Acces”
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"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
When are they going to add sudont? You know, the NT version of sudo 😹
More like
SudoExW
I’ve been using gsudo for a long time, its a game changer.
It took them just under half a century! Good job!
“Look what they need to mimic a fraction of our power!”
— something, something Arch BTW
FINALLY! It only took them WAY TOO MANY FUCKING YEARS! Good job catching up to literal decades-old practices, guys! How do you like living in the 1990s?
Man, I’ll almost miss having to run a VNC session in parallel with WinRM to click on the UAC popup.
Windows is way ahead of the other operating systems. Not even gonna name them because they’re worthless
