I don't have much to add, but seeing sudo.exe in one of the screenshots made me shudder a little. Also, can MS get away with blatantly ripping off this functionality? Taking not just the concept,...
I don't have much to add, but seeing sudo.exe in one of the screenshots made me shudder a little.
Also, can MS get away with blatantly ripping off this functionality? Taking not just the concept, but the name as well? I understand they totally will, because the linux foundation probably has better fights to pick, it just doesn't seem right.
No, please, harmonize further. I don't want to remember dir on windows and ls on Linux. The number of times I've auto piloted ls into a command prompt (before power shell was a thing) has made me...
No, please, harmonize further. I don't want to remember dir on windows and ls on Linux. The number of times I've auto piloted ls into a command prompt (before power shell was a thing) has made me appreciate when at least the basic commands just work across systems.
Microsoft has actually added aliases for a lot of popular *nix tools that map to their PowerShell counterparts. It's convenient. However one thing I like about PowerShell is how verbose all the...
Microsoft has actually added aliases for a lot of popular *nix tools that map to their PowerShell counterparts. It's convenient.
However one thing I like about PowerShell is how verbose all the command names are, as it makes understanding what a script does a lot easier without having to consult a bunch of man pages. So I would hope that they keep using verbose names with Unix-y aliases.
I agree, I like the verbose cmdlet names when I'm writing a Windows specific automation or tool, but prefer the aliases when I'm using an interactive shell and just need to traverse a few...
I agree, I like the verbose cmdlet names when I'm writing a Windows specific automation or tool, but prefer the aliases when I'm using an interactive shell and just need to traverse a few directories, look around, and do some bulk operations.
This is a completely new implementation that happens to use a similar name. Even if not, Sudo is not owned by the Linux Foundation, it's owned by Todd Miller who licenses it extremely liberally:...
This is a completely new implementation that happens to use a similar name.
Reading about the ongoing CrowdStrike fallout, I have the same sinking feeling. Microsoft’s security track record has been abysmal lately. As Steve Gibson would say, what could possibly go wrong?
Reading about the ongoing CrowdStrike fallout, I have the same sinking feeling. Microsoft’s security track record has been abysmal lately. As Steve Gibson would say, what could possibly go wrong?
How was the CrowdStrike fiasco Microsoft's fault? The bug was in CrowdStrike's kernel driver. Buggy kernel modules in Linux can just as easily cause a kernel panic, and in fact CrowdStrike's own...
How was the CrowdStrike fiasco Microsoft's fault? The bug was in CrowdStrike's kernel driver. Buggy kernel modules in Linux can just as easily cause a kernel panic, and in fact CrowdStrike's own Linux product has done it before. It is a risk inherent with any third party code that runs in ring 0.
You’re absolutely right, I shouldn’t have implied a connection between the two. All I meant was that the CrowdStrike incident demonstrated how reliant the world is on Windows systems and what can...
You’re absolutely right, I shouldn’t have implied a connection between the two. All I meant was that the CrowdStrike incident demonstrated how reliant the world is on Windows systems and what can happen when they fail en masse. And, also, Microsoft has had a terrible security track record lately, and they’ve been lucky not to have been responsible for something on the scale. But I worry it’s only a matter of time, the way things are going.
Why is this news? You can just run CMD.exe as administrator, and, like, bam, you've got admin rights. Anyone who has been admin'ing Windows boxes for any length of time knows this.
Why is this news? You can just run CMD.exe as administrator, and, like, bam, you've got admin rights. Anyone who has been admin'ing Windows boxes for any length of time knows this.
I don't have much to add, but seeing sudo.exe in one of the screenshots made me shudder a little.
Also, can MS get away with blatantly ripping off this functionality? Taking not just the concept, but the name as well? I understand they totally will, because the linux foundation probably has better fights to pick, it just doesn't seem right.
No, please, harmonize further. I don't want to remember dir on windows and ls on Linux. The number of times I've auto piloted ls into a command prompt (before power shell was a thing) has made me appreciate when at least the basic commands just work across systems.
Microsoft has actually added aliases for a lot of popular *nix tools that map to their PowerShell counterparts. It's convenient.
However one thing I like about PowerShell is how verbose all the command names are, as it makes understanding what a script does a lot easier without having to consult a bunch of man pages. So I would hope that they keep using verbose names with Unix-y aliases.
I agree, I like the verbose cmdlet names when I'm writing a Windows specific automation or tool, but prefer the aliases when I'm using an interactive shell and just need to traverse a few directories, look around, and do some bulk operations.
I mean, sudo predates Linux by like 15 years.
Here's the license
And su goes back 50 years!
https://en.m.wikipedia.org/wiki/Su_(Unix)
Elevating privileges isn't exactly a new thing
Reading about the ongoing CrowdStrike fallout, I have the same sinking feeling. Microsoft’s security track record has been abysmal lately. As Steve Gibson would say, what could possibly go wrong?
How was the CrowdStrike fiasco Microsoft's fault? The bug was in CrowdStrike's kernel driver. Buggy kernel modules in Linux can just as easily cause a kernel panic, and in fact CrowdStrike's own Linux product has done it before. It is a risk inherent with any third party code that runs in ring 0.
You’re absolutely right, I shouldn’t have implied a connection between the two. All I meant was that the CrowdStrike incident demonstrated how reliant the world is on Windows systems and what can happen when they fail en masse. And, also, Microsoft has had a terrible security track record lately, and they’ve been lucky not to have been responsible for something on the scale. But I worry it’s only a matter of time, the way things are going.
Why is this news? You can just run CMD.exe as administrator, and, like, bam, you've got admin rights. Anyone who has been admin'ing Windows boxes for any length of time knows this.
Too, in theory, you can limit what is sudo’d versus an open admin command prompt.
you can also use
suon linux to achieve the same effect but people often choose to usesudoinstead