Cyberdefense/DeepBlueCLI
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Minor update, added Set-ExecutionPolicy bypass example

Browse Source
This commit is contained in:
Eric Conrad
2019-04-30 17:12:51 -03:00
committed by GitHub
parent ae08b49ffc
commit 4514af7f4a
1 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@ -1,6 +1,6 @@
# DeepBlueCLI # DeepBlueCLI
DeepBlueCLI 2.0 DeepBlueCLI 2.01
Eric Conrad, Backshore Communications, LLC Eric Conrad, Backshore Communications, LLC
@ -30,12 +30,18 @@ If you see this error:
disabled on this system. For more information, see about_Execution_Policies at disabled on this system. For more information, see about_Execution_Policies at
http://go.microsoft.com/fwlink/?LinkID=135170.` http://go.microsoft.com/fwlink/?LinkID=135170.`
You must run Set-ExecutionPolicy as Administrator, here is an example: You must run Set-ExecutionPolicy as Administrator, here is an example (this will warn every time you run a ps1 script):
`Set-ExecutionPolicy RemoteSigned` `Set-ExecutionPolicy RemoteSigned`
This command will bypass Set-Execution entirely:
`Set-ExecutionPolicy Bypass`
See `get-help Set-ExecutionPolicy` for more options. See `get-help Set-ExecutionPolicy` for more options.
Please note that "Set-ExecutionPolicy is not a security control" (quoting @Ben0xA)
## Examples: ## Examples:
### Process local Windows security event log: ### Process local Windows security event log: