From a233d60908d5442214ac6f5726c89f4d0b41418d Mon Sep 17 00:00:00 2001 From: bitform Date: Sun, 20 Jan 2013 21:34:37 -0500 Subject: Added 'CodeExecution' Module * I unfortunately needed to change the names of Inject-Shellcode and Inject-Dll to Invoke-Shellcode and Invoke-DllInjection in order to confirm to proper verb naming. --- CodeExecution/Usage.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 CodeExecution/Usage.md (limited to 'CodeExecution/Usage.md') diff --git a/CodeExecution/Usage.md b/CodeExecution/Usage.md new file mode 100644 index 0000000..f39a1e5 --- /dev/null +++ b/CodeExecution/Usage.md @@ -0,0 +1,12 @@ +To install this module, drop the entire CodeExecution folder into one of your module directories. The default PowerShell module paths are listed in the $Env:PSModulePath environment variable. + +The default per-user module path is: "$Env:HomeDrive$Env:HOMEPATH\Documents\WindowsPowerShell\Modules" +The default computer-level module path is: "$Env:windir\System32\WindowsPowerShell\v1.0\Modules" + +To use the module, type `Import-Module CodeExecution` + +To see the commands imported, type `Get-Command -Module CodeExecution` + +For help on each individual command, Get-Help is your friend. + +Note: The tools contained within this module were all designed such that they can be run individually. Including them in a module simply lends itself to increased portability. \ No newline at end of file -- cgit v1.2.3