Sudo for Windows
321–330 of 439 posts
Re: Sudo for Windows
#322Earlier quoted context omitted.
Linux is just some [explitive deleted] imitation of Unix, where the sudo command originated. I run Windows as my primary development environment because it's better. Linux and other OSes run in VMs.
I don't think you should be downvoted for answering parent's question. It's helpful for understanding a mindset that not everyone possesses. Which version of Windows do you currently run, and what do you feel Windows has or does that makes it superior for your development work?
Windows also stable and performs well, ie no silly kludges needed like oom-killer.
I usually stay a bit behind the curve, roughly keeping with the old "don't upgrade until service pack 2 is released" adage. Just installed Windows 11 on my work machine, running Windows 10 at home.
Re: Sudo for Windows
#323Yep, 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…
Re: Sudo for Windows
#324https://fosstodon.org/@serghei@mastodon.social/1119009868252...
Re: Sudo for Windows
#325Re: Sudo for Windows
#326Earlier quoted context omitted.
I disagree. Although this "Sudo for Windows" is not a one-to-one port from Linux, it does the same function which is to elevate a unprivileged command. Imagine if they announce "Introducing Dosu for Windows", you won't know what the hell that is without reading at least the first paragraph.
In addition to not being a one-to-one port, Sudo for Windows is a completely unrelated command. > it does the same function which is to elevate a unprivileged command That's only one of the use cases of Sudo. Here's a description of Sudo from the official manual [1]: > sudo, sudoedit — execute a command as another user Sudo for Windows can't do that. It's mentioned in its FAQ: > the sudo command on Windows does not s…
Oh, that's a good counter-example to your own point: 99% of people who use cat don't care about this functionality.
Re: Sudo for Windows
#327Yep, 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)?
> Enable Sudo
> Enables the sudo command
If I were a scammer I could make up an acronym or something that sudo means and trick someone into turning this on because the toggle doesn't actually describe what it is so I can just weave my own narrative.
Re: Sudo for Windows
#328Considering the way PowerShell commands go, I assume this will be: RunWithAllTheElevatedPermissionsPossible --YesEvenThose .\inthisfolder.folder\. grep : The term 'grep' is not recognized....
It's evident that you haven't used PowerShell. Almost all commands in PowerShell have short aliases. For instance, instead of typing 'Get-ChildItem', you can simply use 'gci', which stands for the first letters of each word. Unlike Bash and other shells, where you must learn various Domain-Specific Languages (DSLs) to handle XML, JSON, YAML, etc., PowerShell allows you to use its native language to work with any data…
Re: Sudo for Windows
#329Earlier quoted context omitted.
Opening a terminal in admin window which means any commands you put in that windows will always have admin privilege, no matter what. What does Sudo is to only provide the root/admin privileges for specific inputted command. Once it is done, it goes back to user privileges. This way, the terminal window didn't need to end the session to go back to user privileges.
That's a very slim proposition value, especially when multiple commands in a row require admin privileges.
Personally I think it's way more likely the admin command is the one off like installing something, changing a setting and then everything else before and between it are user commands that don't need to be in admin space most of the time.
Re: Sudo for Windows
#330We already have runas for years now. This looks like one of those KPI fulfilling projects.
> Runas /user:administrator "application.exe"
Think this might be why it's not very well known compared to sudo.