Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Sudo for Windows

devblogs.microsoft.com

Post reply on HN
Print view View original

111–120 of 439 posts

Re: Sudo for Windows

#111

Post by Springtime »

neurostimulant wrote: post #78
zadjii wrote: 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…

I think they should've named it something else to avoid confusion, especially if it doesn't have the same behavior as unix sudo. If it has different arguments and features, imagine the confusion of unsuspecting users searching how to use sudo in the future.

> especially if it doesn't have the same behavior as unix sudo... imagine the confusion of unsuspecting users searching how to use sudo in the future.

It's hard to imagine a company that size would name it so deliberately without realizing it would cause confusion in search engine results and such.

A good faith assumption would be they wanted to make Windows more familiar to users of both but it also means that Windows will get mentioned in more Linux results over time to disambiguate it.

Re: Sudo for Windows

#112

Post by NikkiA »

dundarious wrote: post #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 clipbo…

Same here, and if you look at the output of whoami /priv you'll find that using luke's sudo provides exactly the same priviledge escalation as 'run as administrator' does

Re: Sudo for Windows

#113

Post by NikkiA »

djbusby wrote: post #18
SushiHippie wrote: post #3

https://github.com/microsoft/sudo/issues/11 Interesting > Reserved > not blank! > We like to camp nice round number issues like this one, for future use. Can you reuse GitHub issue numbers, or what could be their intention here?

> nice round number issues But the number is 11? Is this Spinal Tap?

'All 1s' has history at MS...

Re: Sudo for Windows

#116

Post by calamari4065 »

aksss wrote: post #103
calamari4065 wrote: post #96

Earlier quoted context omitted.

Having the sudo command open an entirely separate terminal as an admin user is absolutely ridiculous and completely on brand for Microsoft. Along with the UAC dialog, I can't think of a worse way for sudo to behave. What's wrong with entering your password for sudo? How is UAC more secure than a password?

If you’re running as local admin you just get the dialog, but you’re not using a local admin as your daily driver user acct, right? ..Right? :) If you’re logged in as a standard user, UAC prompts you for new username and password to authenticate and authorize the privileged operation.

Seems like a horribly convoluted way to manage permissions. Also I have never heard anyone suggest you shouldn't use a local admin account. That's the exact problem UAC was meant to solve.

Having used an unprivileged Windows account, all I can say is no thanks. It's a huge burden if you do anything even slightly more complex than Facebook and email.

As a blanket policy at work, all programmers are admins, everyone else is not. Except when someone is doing a task that requires elevation every five minutes. I'm the only admin on site and it's an unbelievable waste of my time to sit next to someone so I can put in my password every time they click a box. We make those users admins because there's simply no other way to manage it.

Re: Sudo for Windows

#117

Post by timnetworks »

Springtime wrote: post #111
neurostimulant wrote: post #78

Earlier quoted context omitted.

I think they should've named it something else to avoid confusion, especially if it doesn't have the same behavior as unix sudo. If it has different arguments and features, imagine the confusion of unsuspecting users searching how to use sudo in the future.

> especially if it doesn't have the same behavior as unix sudo... imagine the confusion of unsuspecting users searching how to use sudo in the future. It's hard to imagine a company that size would name it so deliberately without realizing it would cause confusion in search engine results and such. A good faith assumption would be they wanted to make Windows more familiar to users of both but it also means that Windo…

>It's hard to imagine a company that size would name it so deliberately without realizing it would cause confusion in search engine results and such.

same microsoft as where I'm from?

Re: Sudo for Windows

#118

Post by londons_explore »

zadjii wrote: post #67
dist-epoch wrote: post #62

Earlier quoted context omitted.

Putting Microsoft in the UAC prompt is indeed weird. It should be the info of the target binary. This feature sounds a bit rushed, and it's early preview, maybe they fix it by the final release.

Yea, that's a limitation of UAC at this point, and probably not one we can avoid. The "Show details" dropdown on the dialog does however show the commandline you requested, so at least that's one way of making sure it's the thing you ran

A tool like sudo should probably be sufficiently integrated with UAC to be able to customize that dialogue box...

Re: Sudo for Windows

#120

Post by VagabundoP »

zadjii wrote: 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…

ha, thank you! I don't need it often but I have cursed for the want of it in Windows powershell.
Post reply on HN