aljaz/Interlace
1
1
Fork 0
mirror of https://github.com/codingo/Interlace.git synced 2025-12-18 15:24:23 +01:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #9 from codingo/glob-readme

Browse Source 
Updating readme with glob updates
This commit is contained in:
Michael Skelton
2019-01-06 20:40:53 +10:00
committed by GitHub
parent af2d70de8a 7f79278009
commit 056ea4e91a
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
README.md
View File

@@ -112,6 +112,15 @@ interlace -t 192.168.12.0/24 -c "vhostscan _target_ -oN _output_/_target_-vhosts
```
This is despite VHostScan not having any inbuilt CIDR notation support. Since Interlace expands the notation before building a queue of threads, VHostScan for all intents is only receiving a list of direct IP addresses to scan.
## Glob notation with an application that doesn't support it
Interlace automatically expands glob ranges when starting threads. This allows you to pass glob ranges to a variety of applications:
To run a virtual host scan against every target within 192.168.12.* using a direct command you could use:
```bash
interlace -t 192.168.12.* -c "vhostscan _target_ -oN _output_/_target_-vhosts.txt" -o ~/scans/ -threads 50
```
Yet again, VHostScan does not having any inbuilt glob range format support.
## Threading Support for an application that doesn't support it
Run a [virtual host scan](https://github.com/codingo/VHostScan) against each host in a file (target-lst.txt), whilst also limiting scans at any one time to 50 maximum threads.