| Age | Commit message (Collapse) | Author | Files | Lines | 
 | 
 | 
 | 
 | 
 | 
Fixes issue #70
 | 
 | 
Incorporates idea from @obscuresec in issue #50.
 | 
 | 
 | 
 | 
Added ConvertFrom-UACValue to convert binary UAC values to human readable format.
Corrected logic in Set-ADObject.
 | 
 | 
 | 
 | 
 | 
 | 
Updated README.md's
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
This reverts commit a0ab599810f8f05a9bf24850fb9104516b71abb7.
 | 
 | 
 | 
 | 
 | 
 | 
Removed extraneous parameters
Removed the following extraneous parameters:
-PEPath
-PEUrl
The functionality they provided can be easily replicated in code outside
of Invoke-ReflectivePEInjection. i.e. it should be up to the user how
they might want to download a PE before loading it. That should not be
dictated by Invoke-ReflectivePEInjection.
 | 
 | 
This reverts commit 0eb520e31f97bc0ca83bd2c1546a18dd97e09d79.
 | 
 | 
Removed the following extraneous parameters:
-PEPath
-PEUrl
-ComputerName
The functionality they provided can be easily replicated in code outside
of Invoke-ReflectivePEInjection. i.e. it should be up to the user how
they might want to download a PE before loading it. That should not be
dictated by Invoke-ReflectivePEInjection.
 | 
 | 
 | 
 | 
This was only ever intended to be a PoC. I'll bring this back if
requested but it exhibits duplicate functionality.
 | 
 | 
 | 
 | 
 | 
 | 
Those who wish to load this project into VS 2015 with Adam Driscoll's
PowerShell VS extension may now do so.
 | 
 | 
This should have only ever been a shellcode runner. Those wishing to
integrate this with Metasploit should generate a shellcode payload with
msfvenom.
 | 
 | 
now. :P
 | 
 | 
 | 
 | 
This reverts commit 5a812ce82361bf65443fc9c545c091e21e98fe80.
 | 
 | 
 | 
 | 
Fix for multi-processor systems
 | 
 | 
Fix processor architecture detection for multi-processor systems.
 | 
 | 
 | 
 | 
Added New-VolumeShadowCopy and Remove-VolumeShadowCopy Cmdlets
 | 
 | 
- Changed Remove-VSC to have a single mandatory parameter (DevicePath)
- Updated New-VSC to check initial state of the VSS Service and return
VSS to its inital state after execution
 | 
 | 
 | 
 | 
Fix for headings in wrong order
 | 
 | 
The column headings in the log file are out of order, e.g.
```
"TypedKey","Time","WindowTitle"
"Document1 - Word","[Shift]","01-05-2015:20:53:29:28"
"Document1 - Word","[Shift][Shift]","01-05-2015:20:53:29:31"
"Document1 - Word","[Shift]","01-05-2015:20:53:29:38"
```
The "WindowTitle" should be the first column heading like this,
```
"WindowTitle","TypedKey","Time"
"Document1 - Word","[Shift]","01-05-2015:20:53:29:28"
"Document1 - Word","[Shift][Shift]","01-05-2015:20:53:29:31"
"Document1 - Word","[Shift]","01-05-2015:20:53:29:38"
```
 | 
 | 
This fixes the URI bug submitted by @enigma0x3. Thank you for the PR as well! A legacy switch is added in case anyone is relying on this script and an older meterpreter handler. 
Proxy support is added to grab the default proxy by way of a switch.
The default user-agent is grabbed from the registry instead of being a static string.
I tested this on a Windows 7 SP1 (both x86 and 64-bit) and Windows 8.1 (64-bit) with an older handler and an updated one.
 | 
 | 
Thanks, @aconite33 for the suggestion.
- TripleDESCryptoServiceProvider is now used as the crypto algorithm
because it won't break the script when FIPS compliance is enabled in the
registry.
- I actually implemented the InitializationVector parameter
- Cleaned up the output script
- Cleaned up comment-based help
 | 
 | 
Update to latest Mimikatz, add sanity checks
 | 
 | 
Updated to the latest Mimikatz build. Added sanity checks to ensure that
32bit PowerShell isn't being run on a 64bit OS which will cause Mimikatz
to fail.
 | 
 | 
 | 
 | 
These things happen
 | 
 | 
Adding PEBytes parameter
 | 
 | 
Added PEBytes parameter for reflectively loading a PE file passed as a
byte array to the script.
 | 
 | 
Bugfix: Resolving ordinals in remote dll injection
 | 
 | 
Thanks to sixdub for finding and fixing a bug when resolving functions
by ordinal in remote processes.
 | 
 | 
When file paths were specified, they were not being properly validated.
 | 
 | 
https://github.com/mattifestation/PowerShellArsenal
PowerSploit will now stay true to its roots of being a purely offensive
PowerShell module.
 | 
 | 
 |