PowerSploit - PowerSploit - A PowerShell Post-Exploitation Framework

Age	Commit message (Collapse)	Author	Files	Lines
2015-12-16	Removed all version numbers from scripts	Matt Graeber	1	-2/+0
	Scripts in a module should not be individually versioned. Only the module should be versioned.
2015-10-30	Update Invoke-TokenManipulation.ps1	FixTheExchange	1	-2/+0
	Removed 2 unnecessary lines.
2015-10-30	Update Invoke-TokenManipulation.ps1	FixTheExchange	1	-4/+11
	Windows 10 breaks the current version of Invoke-TokenManipulation.ps1 because wininit is now a protected processes. Rather than hardcoding to a specific process to obtain a SYSTEM token, it's better to enumerate all processes running as SYSTEM and find one that works. I have updated the script to version 1.12 and added logic on lines 1689-1696 to make sure it can successfully grab a SYSTEM token necessary to function.
2014-09-28	Added -PassThru to Invoke-TokenManipulation	clymb3r	1	-5/+35
	Thanks to Run Mariboe for the contribution to Invoke-TokenManipulation adding the -PassThru flag for newly created processes. Version increased to 1.11.
2014-01-11	Merge pull request #25 from clymb3r/master	Matt Graeber	1	-32/+142
	Bug fixes for Invoke-TokenManipulation
2014-01-10	Bug fixes for Invoke-TokenManipulation	clymb3r	1	-32/+142
	Processes could not be started when the script was being run from Session 0. The fix is to use the CreateProcessAsUserW function when running in Session 0. This API requires SeAssignPrimaryTokenPrivilege priviege, so for non-session0 calls I still use CreateProcessWithTokenW which does not require special privileges.
2013-11-13	Normalized all scripts to ASCII encoding	mattifestation	1	-1/+1

2013-11-04	Updated Invoke-TokenManipulation help	clymb3r	1	-2/+2

2013-11-03	Adding Invoke-TokenManipulation	clymb3r	1	-0/+1773