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

221–230 of 439 posts

Re: Sudo for Windows

#221

Post by righthand »

a_vanderbilt wrote: post #37
righthand wrote: post #24

Earlier quoted context omitted.

I don’t disagree. How I think it will happen: Backwards compatibility will start to stray at Microsoft (their last bastion), leading to WINE becoming the go to tool for backwards compat support. Microsoft will create a linux variant or maybe just a DE and the rest will be history (just as Libre Office has begun to supersede MS Office). It is a matter of will and time that C-Suite will want to eliminate labor around W…

In what business segment is Libre Office superseding MS Office? Furthermore, NT supports "personalities". Why bother with a full Linux kernel when they could adopt the personality a la SUA?

Superseding in compatibility. I’m not talking about business segments.

They don’t have to adopt it, they will probably fork it.

Re: Sudo for Windows

#222

Post by bsimpson »

jimt1234 wrote: post #204

Side note that I've always found interesting: sudo is almost entirely maintained by one dude: https://github.com/sudo-project/sudo/graphs/contributors

If he's in Nebraska, then it's literally https://xkcd.com/2347/

According to his website, he's been the maintainer for 30+ years.

Re: Sudo for Windows

#223

Post by nine_k »

Repulsion9513 wrote: post #172
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…

Why can't you do this with the tool that already exists to do the exact same thing, called runas?

Does it have a policy editor comparable to the /etc/sudoers file? Sudo is interesting not because it just allows to assume admin privileges for a moment; it allows to give access in a finely-grained manner, and not exclusively admin access.

Just scrolling through the documentation [1] gives some idea. Examples in the end may surprise the reader with the variety of capabilities.

[1]: https://www.man7.org/linux/man-pages/man5/sudoers.5.html

Re: Sudo for Windows

#224

Post by e40 »

Repulsion9513 wrote: post #172
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…

Why can't you do this with the tool that already exists to do the exact same thing, called runas?

Been using it for a decade or more. Came to make this comment.

Re: Sudo for Windows

#225

Post by zadjii »

codeflo wrote: post #128

Sad that it's Windows 11 only. I can't upgrade. I have a normal, recent PC that I dual boot with Linux, and Microsoft wants me to keep Windows 10 in that constellation. Upgrading is prevented by a silly if statement, and there's nothing I can do. It's the first time a software vendor actively doesn't want me to to have their latest software, but it is what it is.

We're working on backporting it to Windows 10. For updates, you can follow https://github.com/microsoft/sudo/issues/2

Re: Sudo for Windows

#226

Post by dsalzman »

bsimpson wrote: post #222
jimt1234 wrote: post #204

Side note that I've always found interesting: sudo is almost entirely maintained by one dude: https://github.com/sudo-project/sudo/graphs/contributors

If he's in Nebraska, then it's literally https://xkcd.com/2347/ According to his website, he's been the maintainer for 30+ years.

Boulder,CO per his github

Re: Sudo for Windows

#227

Post by zadjii »

Repulsion9513 wrote: post #177
zadjii wrote: 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.

There are several ways to do sudo for Windows already, to the extent this program does sudo for Windows. In other words, you're not actually solving the reason people are asking you for sudo for Windows. How do I configure my sudoers policy to allow someone to run a specific application (and only that application) through sudo? THAT is the magic of sudo. Sudo is not just "use your own password for root" like you seem…

I live by a one step at a time philosophy. It's better to make some incremental progress here, now, and open the door for future progress in this space too. Just like the Terminal - what we're putting out here in the first versions is just the first thing we feel comfortable with people using. We've got lots of ideas for more things to add, just, one step at a time :)

Re: Sudo for Windows

#228

Post by zadjii »

squeaky-clean wrote: post #183

Why is Inline not the default option?

There are security implications for running elevated processes connected to unelevated console/terminal windows. "New window" mode avoids those security concerns. A secure-by-default posture seemed prudent.

Re: Sudo for Windows

#229

Post by eviks »

lIl-IIIl wrote: post #88
pjmlp wrote: post #21

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

The comment in the article links to this explanation: https://learn.microsoft.com/en-us/windows/sudo/#how-is-sudo-...

Thanks for the link, is this the only benefit?

> You can choose to connect the elevated process to the current console window with the disableInput and normal configuration options. This is not supported with runas.

I also thought that using current environment vars you have set/changed in the terminal is an extra benefit, but that's not listed, so it's not?

Post reply on HN