| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2015-12-16 | Removed all version numbers from scripts | Matt Graeber | 1 | -4/+0 | |
| Scripts in a module should not be individually versioned. Only the module should be versioned. | |||||
| 2013-11-13 | Normalized all scripts to ASCII encoding | mattifestation | 1 | -1/+1 | |
| 2013-10-22 | Fix for hostfiles option in powershell 2 | webstersprodigy | 1 | -2/+2 | |
| 2013-06-25 | IPv6 support in hosts param | Rich Lundeen | 1 | -11/+14 | |
| 2013-06-18 | fixing EOL spaces (again, sorry) | Rich Lundeen | 1 | -3/+0 | |
| 2013-06-18 | fixing EOL spaces | Rich Lundeen | 1 | -24/+13 | |
| 2013-06-18 | Addressed mattifestation feedback | Rich Lundeen | 1 | -235/+275 | |
| 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" | |||||
| 2013-06-11 | small style update | Rich Lundeen | 1 | -3/+3 | |
| 2013-06-11 | Powershell 2.0 fixes - should work now | Rich Lundeen | 1 | -124/+165 | |
| 2013-06-10 | fixing powershell 2.0 compat | Rich Lundeen | 1 | -6/+18 | |
| 2013-06-09 | removed a few comments | Rich Lundeen | 1 | -6/+0 | |
| 2013-06-09 | added invoke-portscan module | Rich Lundeen | 1 | -0/+1012 | |