Live data from Hacker News

Sudo for Windows

devblogs.microsoft.com

81–90 of 439 posts

Re: Sudo for Windows

#82

What's the difference from opening a Terminal (Admin) window? Just that you can run a single command as admin? I must be missing something here

Opening a terminal in admin window which means any commands you put in that windows will always have admin privilege, no matter what. What does Sudo is to only provide the root/admin privileges for specific inputted command. Once it is done, it goes back to user privileges. This way, the terminal window didn't need to end the session to go back to user privileges.

Why is admin privilidge even a thing? Ask for the god damn specific resource you want access to and I'll answer yes or no!

Re: Sudo for Windows

#83
post #58
post #21

We already have runas for years now. This looks like one of those KPI fulfilling projects.

> This looks like one of those KPI fulfilling projects It actually wasn't. This has been one of the top community requests for the Windows Command Line for years. Literally, for like, the entire 8 years I've been here, we've been talking about if there was a way to do Sudo for Windows. This was done because it makes developers happy, plain and simple. If that's a KPI, then that's the one we're optimizing for.

What is different about sudo vs runas?

Re: Sudo for Windows

#84
If everyone thinks this is so great (just judging by the number of times it's appeared in the HN top 30), why don't they just run linux, instead of some sh!t immitation?

Everyone knows, if you can C colon, your running a M$ product...

Re: Sudo for Windows

#86

Earlier quoted context omitted.

I have been continually disappointed that Microsoft has not released a seamless Windows virtualization system. WindowsX would run the new, redesigned APIs, but all of the legacy could run inside a sandboxed system to give the world the required decades to finally transition.

Windows Subsystem for Windows?

How about, “Winception”

Re: Sudo for Windows

#87
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 clipboard history -- does not clear the current value). There is a UAC prompt, but it's perfectly adequate for interactive work.

Re: Sudo for Windows

#89
post #83
post #58

Earlier quoted context omitted.

> This looks like one of those KPI fulfilling projects It actually wasn't. This has been one of the top community requests for the Windows Command Line for years. Literally, for like, the entire 8 years I've been here, we've been talking about if there was a way to do Sudo for Windows. This was done because it makes developers happy, plain and simple. If that's a KPI, then that's the one we're optimizing for.

What is different about sudo vs runas?

https://learn.microsoft.com/en-us/windows/sudo/#how-is-sudo-...

Re: Sudo for Windows

#90
post #7
post #2

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…

Nice to see the author here! I have to say: I really like whats going on in Windows world from a developer perspective in the recent years. I am a hardcore Linux fanboy for decades but I have to admit that PowerShell, WSL, vscode, Windows Terminal and the recent open source strategy sounds very appealing to me. This is something MS/Win does much better in recent days compared to, for instance, Apple/Mac OS. I would l…

Windows change is welcoming, yet still not quality. As stated by someone below, sudo is https://www.sudo.ws/. Microsoft should give it a proper distinctive name lie wsudo or psudo. Little thinks like is compounds the issues with Windows / Microsoft.

Even continually sticking to old design patterns causes issues in development and deployment. Big name companies do not trust applications running on hosted Windows because of their current business practices. Microsoft does not even have a means to provided ease of deployment for air-gap system. This is the only way some big business will let products hosted on Windows to be in their facilities.

Windows as become more problematic for me because of all the layers of security that need to be applied for companies to trust Windows. This causes issues such as having to stop typing because Visual Studios or VSCode cannot process key strokes in real time.

Localization translation text standard still does not allow for containing singular and plural in the same key. Translations should be easily to update so the client can improve wording on the fly. Microsoft still recommends using resx and compiling a DLL.

.....

Post reply on HN