News for hackers. Stuff that matters.

A comment on Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build. Parent comment

Re:Microsoft Replaces Command Prompt with PowerShell in Late... by noinsight on Friday November 18, 2016 @09:34PM (#12991713)
My problem with the Execution Policy is that it's useless in practice since it doesn't actually prevent anything (so it annoys me every time). What was the motivation for adding it since it's not a real security feature? If it actually prevented executing stuff full stop it would be cool. The signed script concept is cool... I wish I could do that with Python.

Was it just to prevent accidental script execution?

[ Parent | on HN ]
Re:Microsoft Replaces Command Prompt with PowerShell in Late... by JeffreySnover on Friday November 18, 2016 @10:45PM (#12991962)
That is correct (prevent accidental script execution).

It is ABSOLUTELY NOT a security mechanism. That is why we we support this:

Set-ExecutionPolicy -ExecutionPolicy Bypass

I wanted to make it:

Set-ExecutionPolicy -ExecutionPolicy DoAnythingBecauseTExecutionPolicyIsNOTASecurityFeature

But the team didn't like that. (I should have overruled them on that one :-) ).

Jeffrey Snover [MSFT]

[ Parent | on HN ]