91–100 of 439 posts
Earlier quoted context omitted.
I have been continually disappointed that Microsoft has not released a seamless Windows virtualization system. WindowsX would run the new, redesigned APIs, but all of the legacy could run inside a sandboxed system to give the world the required decades to finally transition.
Windows Subsystem for Windows?
Earlier 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.
Why is admin privilidge even a thing? Ask for the god damn specific resource you want access to and I'll answer yes or no!
If everyone thinks this is so great (just judging by the number of times it's appeared in the HN top 30), why don't they just run linux, instead of some sh!t immitation? Everyone knows, if you can C colon, your running a M$ product...
I run Windows as my primary development environment because it's better. Linux and other OSes run in VMs.
This is like when PowerShell hijacked curl all over again...
If it's just an alias for "runas" that presents a UAC prompt window I will be disappointed.
Initially I thought ur concern is crazy as hell, because who would implement it in such a painful way? But then I read >When elevating a process from the command-line with sudo, a UAC dialog will appear asking the user to confirm the elevation: LOL But it seems like there are other ways to use it without this dialog >In this configuration, sudo.exe will launch a new elevated console window and run the command in that…
Along with the UAC dialog, I can't think of a worse way for sudo to behave.
What's wrong with entering your password for sudo? How is UAC more secure than a password?
Earlier quoted context omitted.
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.
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…
Can someone detail the differences between this and runas plz?
Next: systemd for windows?
Already there. Windows has had services for a long time managed pretty similarly to systemd/launchd.
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...
sudo on windows has a different risk profile given the malware ecosystem and lack of educated/ trained users. 95% of linux users are developers who understand risk -- though are prone to mistakes 99% of windows users are casual consumers . Let's keep this functionality narrowly accessible : restricted to developer mode and very formal consent. I suggest disabling it if it's unused for a few days this will only rejuve…
There's still the UAC prompt which should help mitigate risk, plus it's locked behind developer settings.