aboutsummaryrefslogtreecommitdiff
path: root/ScriptModification/ScriptModification.psm1
diff options
context:
space:
mode:
authorJon Cave <jon.cave@mwrinfosecurity.com>2016-08-13 12:05:12 +0100
committerJon Cave <jon.cave@mwrinfosecurity.com>2016-08-13 12:14:35 +0100
commit9b365e82b1bcf9957179ada3e1df4f6feb1c5888 (patch)
tree74284b3d4178776a132bedc40af4287db240bef4 /ScriptModification/ScriptModification.psm1
parentfda456338f75c7adb0a26df72de53d78b1ccb6da (diff)
downloadPowerSploit-9b365e82b1bcf9957179ada3e1df4f6feb1c5888.tar.gz
PowerSploit-9b365e82b1bcf9957179ada3e1df4f6feb1c5888.zip
Continuously collect output from background threads
The PowerShell.BeginInvoke<TInput, TOutput>(PSDataCollection<TInput>, PSDataCollection<TOutput>) method[1] is used to collect output from each job into a buffer. This can be read whilst the jobs are still running. Being able to return partial results is particularly useful for long running background threads, such as Invoke-UserHunter -Poll. PowerShell 2.0 doesn't play nicely with generic methods. The technique described in [2] is used to allow this version of BeginInvoke() to be used. [1] https://msdn.microsoft.com/en-us/library/dd182440(v=vs.85).aspx [2] http://www.leeholmes.com/blog/2007/06/19/invoking-generic-methods-on-non-generic-classes-in-powershell/
Diffstat (limited to 'ScriptModification/ScriptModification.psm1')
0 files changed, 0 insertions, 0 deletions