3 August 2014

I hate it when I find a new — and very easy — solution to a problem.  I’ve only recently discovered the parameter -ExecutionPolicy to the powershell.exe application and the value “Bypass.”  It allows you to, you guessed it, bypass whatever execution policy is set even if it’s restricted.  Non-admins can use it too… which at first seems really stupid but the bypass does not elevate anything so if they don’t have rights, they don’t have rights.

Anyway, that’s probably been around forever and I feel really stupid for just learning about it.  I discovered it when I had a script run at startup on a machine that didn’t have an execution policy set to something other than restricted and I saw the command line for the process using that parameter.

Even though I feel really stupid I’m glad I found it 🙂


There are no comments.



You must be logged in to post a comment.

Links

RSS 2.0 Feed

Support

Brave Rewards
This site supports Brave Rewards. Please consider tipping or adding it to your monthly contributions if you find anything helpful!

For other ways: Support

Support this blog! If you have found it helpfu you can send me crypto. Any amount is appreciated!
ETH: 0xBEaF72807Cb5f4a8CCE23A5E7949041f62e8F8f0 | BTC: 3HTK5VJWr3vnftxbrcWAszLkRTrx9s5KzZ | SHIB: 0xdb209f96dD1BdcC12f03FdDfFAD0602276fb29BE
Brave Users you can send me BAT using the browser.