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

351–360 of 439 posts

Re: Sudo for Windows

#351

Post by madeofpalk »

matthews2 wrote: post #13

This smells like when PowerShell aliased curl and wget to a completely different command, with incompatible arguments. https://github.com/PowerShell/PowerShell/pull/1901

As a regular Windows, Linux (via WSL), and macOS user, I'm not confused by the curl/wget alias in Powershell, and I appreciate it. I understand from context that it's not actually curl and has different options. It's much easier than remembering whatever Invoke-HyperText-Transfer-Protocol-Request -Url incantation that's native to Powershell.

Re: Sudo for Windows

#352

Post by coggs »

shortformblog wrote: post #114

Just pointing out that this is a really good tweet by the co-creator of sudo: https://twitter.com/BobCoggeshall/status/1755681410596192604

I guess if we were on a conquest for universal adoption we can now say we've succeeded..

Re: Sudo for Windows

#353

Post by codeflo »

yellowapple wrote: post #208
c-hendricks wrote: post #150

Earlier quoted context omitted.

Ventoy will also help them, there's absolutely something they could do.

You can also boot the normal installer, hit Shift+F10, run regedit, and set HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig\BypassTPMCheck to 1.

Unless there's official documentation that this is officially supported, hacks like these can stop working at any moment. For an unimportant machine, sure, use whatever third-party tool to bypass the installer you want. For a production machine, I don't think that's wise.

Re: Sudo for Windows

#354

Post by WhyNotHugo »

mappu wrote: post #253
nine_k wrote: post #223

Earlier quoted context omitted.

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-pag…

You're talking about Sudo for Linux - today's new "Sudo for Windows" doesn't support a sudoers file.

Nitpick: it’s not “Sudo for Linux”, it’s just “sudo” and runs on a wide variety of operating systems aside from Linux. It actually predates Linux by around a decade.

Re: Sudo for Windows

#356

Post by SV_BubbleTime »

soraminazuki wrote: post #276
withinrafael wrote: post #210

Earlier quoted context omitted.

UAC still isn't a security boundary, but rather a defense-in-depth measure.

Shouldn't defense-in-depth be about putting multiple meaningful security measures in place?

Shallow is still a depth.

Re: Sudo for Windows

#357

Post by ape4 »

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.

perhaps `admininator`

Re: Sudo for Windows

#358

Post by hypeatei »

madeofpalk wrote: post #351
matthews2 wrote: post #13

This smells like when PowerShell aliased curl and wget to a completely different command, with incompatible arguments. https://github.com/PowerShell/PowerShell/pull/1901

As a regular Windows, Linux (via WSL), and macOS user, I'm not confused by the curl/wget alias in Powershell, and I appreciate it. I understand from context that it's not actually curl and has different options. It's much easier than remembering whatever Invoke-HyperText-Transfer-Protocol-Request -Url incantation that's native to Powershell.

Sure, it's not confusing once you know about it and remove it.

But, when you install the actual curl and it doesn't work the way you expect, then it's both irritating and confusing. Horrible choice by MSFT.

Re: Sudo for Windows

#359

Post by osigurdson »

Windows should just run Linux. For apps that really need the Windows OS, use something akin to macOS parallels. I really like WSL of course, but would prefer an inverted paradigm.

Re: Sudo for Windows

#360

Post by wongarsu »

osigurdson wrote: post #359

Windows should just run Linux. For apps that really need the Windows OS, use something akin to macOS parallels. I really like WSL of course, but would prefer an inverted paradigm.

The Windows kernel has a lot of features that Linux lacks. Dropping all those features would make a lot of people very angry, especially admins in big corporations.
Post reply on HN