aboutsummaryrefslogtreecommitdiff
path: root/CodeExecution
diff options
context:
space:
mode:
authorRich Lundeen <richard.lundeen@gmail.com>2013-06-18 13:17:06 -0700
committerRich Lundeen <richard.lundeen@gmail.com>2013-06-18 13:17:06 -0700
commit223527d4cdf1fd227dda53ea3768fc57aa1552ce (patch)
tree042732529b88f77215f990fd38f2c3e8166de982 /CodeExecution
parentaf49f5cfaf656597a687c54498d6811b103d2751 (diff)
downloadPowerSploit-223527d4cdf1fd227dda53ea3768fc57aa1552ce.tar.gz
PowerSploit-223527d4cdf1fd227dda53ea3768fc57aa1552ce.zip
Addressed mattifestation feedback
See https://github.com/mattifestation/PowerSploit/pull/6#issuecomment-19289063 1) I like this feedback a lot and took it. 2) I tried going thread only but it got messed up with very large scans. Eventually, I didn't think it was worth the amount of effort to make it reliable with only threads 3) Tried to do this 4) Did this 5) I like the idea in general and I took this one place (top-ports), but not for the two examples you gave. The reasoning is, I want people to be able to specify various options and arrays aren't that flexible. For example, I want people to specify a port list like "80,90,8080-8090". Similar with CIDR, since that's one option, but they could also be specifying hostnames e.g. "google.com,192.168.1.1/24,10.0.0.1"
Diffstat (limited to 'CodeExecution')
0 files changed, 0 insertions, 0 deletions