Introducing Sudo for Windows!
devblogs.microsoft.com
Introducing Sudo for Windows We’re excited to announce the release of Sudo for Windows in Windows 11 Insider Preview Build 26052! Sudo for Windows is a new way for users to run elevated commands directly from an unelevated console session. It is an ergonomic and familiar solution for users who want to elevate a command without having to first open a new elevated console.

Shipped in Windows 11 Insider Preview Build 26052. https://www.tiraniddo.dev/2024/02/sudo-on-windows-quick-rundown.html claims it has a big security problem that makes the program accept calls to elevate from anywhere once first run

Edit:

  1. The security problem has been internally fixed and will be available in the next release
  2. It’s not just an alias for ‘runas’. It seems to be able to configurably block user input for sudo’d commands, retain the existing environment, ditch it and open a new window, and remember that you’ve sudo’d in the last minute or so.
  3. It brings up UAC instead of having you input the password
  • Pilgrim@beehaw.org
    13·
    10 months ago

    I would say “hey that’s just copying” but Microsoft is legally incapable of being wrong, or noticing irony so I’ll leave it be

    • OmnipotentEntity@beehaw.org
      12·
      10 months ago

      If I’m understanding this correctly, it’s not even copying. It’s apparently just a wrapper for the built-in runas command that’s been there since Windows 2000.

      • Mike Griese@mastodon.social
        4·
        10 months ago

        @OmnipotentEntity @Pilgrim it’s actually not just a wrapper for runas. There’s a lot of other plumbing here to get the console handle you’re actually using plumbed to the target application. That’s the magic that lets you actually interact with the elevated process in the same terminal.

        With runas, the target application is just stuck in a separate console window (gross)

        • OmnipotentEntity@beehaw.org
          2·
          10 months ago

          So please forgive me if this is a rather naive question. I haven’t seriously used Windows in nearly 15 years.

          I seem to recall runas being a lot like su, in that you enter the target user’s credentials, rather than your own as in sudo. This works because sudo is a setuid executable, and reads from configuration to find out what you’re allowed to do as the switched user.

          Is the behavior of windows sudo like unix su or unix sudo with regard to the credentials you enter? Can you limit the user to only certain commands?

      • PenguinCoder@beehaw.orgEnglish
        6·
        10 months ago

        Exactly. Windows already has this functionality with runas and this implantation doesn’t improve on it at all.

        • TxzK@lemmy.zip
          5·
          10 months ago

          Classic Microsoft. Just change the look and be done with. No need it to actually improve the internals.

  • Nath@aussie.zone
    11·
    10 months ago

    I was Googling like mad just this week on how to execute a cmdlet as Admin from within a script that isn’t running with elevated privileges. The results all basically came back with some variation of “just run the script as Admin”.

    This is the right way to do it. I’m glad it’s coming.

      • Nath@aussie.zone
        2·
        10 months ago

        That’s where I started, of course - but you can’t combine -verb with -credential. It’s a silly limitation that seems to make sense to Microsoft. What you can do is configure a savecred which you can call with RunAs, but you then need to update that saved credential every time the password changes.

        I do have a $Credential object that has been pulled out of the password safe that has elevation permissions, but can’t seem to apply it non-interactively or without being in an elevated session. This appears to be by design. Not that I intended my comment to turn into a support question. 😀

    • 4dpuzzle@beehaw.orgEnglish
      8·
      10 months ago

      The OpenBSD devs published a mail about it. The irony here is how Microsoft would behave if anybody else copied their concepts, including the name. The treatment is never symmetric or reciprocal.

      • UNIX84@beehaw.org
        10·
        10 months ago

        I mean licensing comes in here. The FOSS licenses allow this. Microsoft EULA and copyright almost certainly does not. But yes, I get the sentiment.

        It’s almost as if all of the FAANG/Magnificent 7 market outperformance the past 15 years was built on the backs of the free labor provided by the FOSS movement. But then they will turn around and claim that non-western companies steal IP, etc and have US intervene to ban competition, or sue in courts. Kind of funny.

        Back to the tech discussion, I’ve been using doas for a few years now instead of sudo. Even on my GNU/Linux machines. It’s a lot simpler to setup for desktop workflow machines.

        • jarfil@beehaw.org
          2·
          10 months ago

          free labor provided by the FOSS movement

          Check out the contributors to Linux, how many of them work for free vs. how many work on behalf of companies.

          There is this pervasive myth that FOSS gets developed by lone wolves working in their spare time, when in reality most of the projects that get any traction, have a financing model behind them.