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

141–150 of 439 posts

Re: Sudo for Windows

#141

Post by marwis »

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

Maybe until UAC is improved you can ship with a launcher process that is signed by publisher "Unknown"?

Re: Sudo for Windows

#142

Post by skeaker »

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.

What do you mean? If it's the TPM requirement, Rufus can whip up a Win11 installer that bypasses that in like a minute.

Re: Sudo for Windows

#143

Post by bigstrat2003 »

madspindel wrote: post #99
cogman10 wrote: post #29

Earlier quoted context omitted.

Already there. Windows has had services for a long time managed pretty similarly to systemd/launchd.

Well, compare how to start syncthing automatically on Windows: https://docs.syncthing.net/users/autostart.html On Debian I could just type: systemctl --user enable --now syncthing.service Native systemd on Windows would be awesome. Microsoft should hire the creator of systemd...

Looking at that page, it looks like syncthing chooses to not provide a Windows service. That is where 100% of the complexity is coming from. If they did provide a Windows service, then it would be as simple as opening the service manager, and setting the startup type from "manual" to "automatic".

It's not fair to blame Windows for the developers of an app not using its features. Similarly, if syncthing didn't bother to create a unit file on Linux, your example would no longer be a simple one liner. That wouldn't be systemd's fault though.

Re: Sudo for Windows

#144

Post by delta_p_delta_x »

al_borland wrote: post #44
Night_Thastus wrote: post #27

Interesting. I've been pretty happy with all the Unix-related updates they've put out lately. WSL has been a godsend and the new terminal and powershell have worked a treat. Glad they seem to be continuing with it.

My theory is that Microsoft is working on eventually moving Windows over to the Linux kernel, and all these things they are doing are setting the stage and preparing for an easier transition.

This comment reminds me of the GIF of Michael Scott screaming 'NO GOD PLEASE NO'[1].

It also tells me that anyone who makes this comment has limited exposure to comparative kernel development. I've always said it, I'll say it now, and I'll say it in the future: the NT kernel is by far the best part of Windows, and it is in many ways superior to the Linux kernel. Furthermore, Windows ships with an absolute metric ton of very nice userspace technologies that either a) don't exist on Linux, or b) are rubbish to use on Linux.

I don't understand why people want everything to converge on the Linux kernel and its userspace. I like open-source as much as everyone else, but 'let's make ALL the things GNU/Linux!' just leads to lack of competition and therefore stagnation and no innovation.

I have a better wish: Microsoft should open-source core Windows technologies, and eventually, the NT kernel itself. Then, it could maintain its official Microsoft® Windows™ distribution with support contracts, while allowing developers to compile and modify WindowsOpen. Something like what it currently does with VS Code.

[1]: https://knowyourmeme.com/memes/no-god-please-no

Re: Sudo for Windows

#145

Post by int_19h »

actinium226 wrote: post #122
ktpsns wrote: post #7

Earlier quoted context omitted.

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…

I'd love to see winget with a command structure that makes sense. Currently if I want to install python via winget, I have to run `winget install -e --id Python.Python.3.11`. -e? --id? What are these for? Why do I have to memorize them? Almost every other package manager just does something like `packagemanager install python`, and then you can supply args for versions if you like. Also winget does not have python 3.…

winget has Python 3.12.2 at the moment, which has been released two days ago.

And you don't have to use --id - you can do `winget install 7zip` etc in cases where there's no ambiguity.

Re: Sudo for Windows

#146

Post by israrkhan »

When I was at Microsoft we did not use to consider UAC as a security boundary, since there were ways to bypass it. (I used to work on windows kernel security). I wonder how security team let this feature get shipped. Or perhaps now they consider UAC as a security boundary.

Re: Sudo for Windows

#147

Post by delta_p_delta_x »

calamari4065 wrote: post #97
Night_Thastus wrote: post #60

Earlier quoted context omitted.

As I said on the other post, I strongly doubt that. It offers few benefits and many roadblocks. It would be a monstrous amount of work, would throw into question many existing security-related certifications, break Microsoft's love of backwards-compatibility, etc. All MS is trying to do is make it easier for developers to develop on Windows for Windows, which it has ample incentive to do both internally and externall…

I'm really amused that the least painful way to develop for Windows on Windows is to just use Linux.

> the least painful way to develop for Windows on Windows is to just use Linux

Eh? Even as a joke, I don't get it.

1. Download Visual Studio 2022 Community Edition

2. Select and install the workloads you need

3. Fire up any boilerplate from the Welcome menu

4. Press the green play button

Sure, it's no `pacman -S base-devel && g++ main.cpp && ./a.out`, but it's not as bad as everyone puts it.

It is a GUI-first operating system, and if you want to write a fast, HiDPI-aware Win32 application today that supports everything from Windows XP to Windows 11 that's < 50 kB, you absolutely can.

Re: Sudo for Windows

#148

Post by gruez »

mappu wrote: post #26
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…

Does the UAC prompt always say "Verified publisher: Microsoft"? Even without controlling stdin, malware at medium integrity could prompt to run a malicious command, and users will only see Microsoft's good name in the popup. Does this elevate within your own account token (i.e. will not work for non-Administrator users), or does it actually switch user (e.g. to LOCAL SYSTEM)?

Can't you already do that today with cmd.exe?

Re: Sudo for Windows

#149

Post by jraph »

Sakos wrote: post #135
jraph wrote: post #132

Earlier quoted context omitted.

> I'm still shocked to this day that we managed to ship this at all Why?

Sorry, have you never read anything about Microsoft before? I'm not sure why people are being so critical of OP.

Look, I'm genuinely curious and we happen to have a MS dev here who could provide interesting first hand insight.

I'm not critical. I don't have enough knowledge on the situation to share criticism on the topic yet.

I could have added "Could you expand on this?" to clarify my intent.

Re: Sudo for Windows

#150

Post by c-hendricks »

skeaker wrote: post #142
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.

What do you mean? If it's the TPM requirement, Rufus can whip up a Win11 installer that bypasses that in like a minute.

Ventoy will also help them, there's absolutely something they could do.
Post reply on HN