Attackers are using social engineering to get users to copy, paste, and run malicious scripts — all while thinking they are helping out the IT team.
Hot take: to Most windows users (not you) probably shouldn’t be able to access power shell or cmd.exe at all.
Accessing powershell is not the issue - that Windows is broken, with a sprinkle of bad permission management by corporations using it is the issue. And the bad permission practices are a direct result of how broken Windows is - I tried a while ago to use it with a fully unprivileged user, just like I do for decades on UNIX and now Linux. It pretty much is impossible without privilege elevation prompts every few minutes.
In a proper environment a user should be able to destroy data they’re working with - but not have the ability to alter the operating system.
That’s not a hot take, that’s empirical fact: https://lifehacker.com/this-chart-shows-how-computer-literate-most-people-are-1789761598
deleted by creator
You can’t in S mode
The stupid thing is you can’t reenter S mode once you’ve left.
Family member needed printer software that wasn’t on MS Store, so I told them we’d need to drop S mode to get it, which meant reducing security. Now I have to be the defacto IT person and the security team for them.
This is similar to how casual users on Windows should be limited to a non-admin account, to limit vectors for malware.
Isn’t it what happens on Mac? I’m told there is a command line on there, but I’ll be damned if I’ve ever met* a Mac addict who’s heard of it, let alone used it.
I’m certainly biased, but we use macOS at work and nearly everyone is familiar with the terminal. We’re developers though, but even our less technical people (product owners and whatnot) know what it is and what it can do.
But yeah, I wouldn’t be opposed to turning on a dev option to enable it though. I use it every day, but most don’t need to (even our devs could configure commands in their IDE).
