Scan [x] Threads

Miserly

May 25 2004, 09:31 PM

Description:
Scan [x] Threads is a modded version of sfind, it's like scan100, scan500 or scan1000.
the only difference is, that you can configure how many threads you want to use for scanning.
so you don't really need anymore 3 tools, if you want 100/500/1000 threads simply change it in config.cfg or via the parameter -config <threadcount>

Overview about Parameters/Options, what you can scan

QUOTE

D:\>scan
Error!

=========Modded Sfind=========
========Version 0.93 By MaXxX ========

Usage: scan <Option> <Parameter>

<Option>:
-config Threads Set
-p <Port|Port-Port> <IP|IP-IP> Scan
-cgi <IP address> Scan
-idq <Start IP> <End IP> Scan
-pri <Start IP> <End IP> Scan
-apache <Start IP> <End IP> Scan
-apache2 <Start IP> <End IP> Scan
-apachechunked <Start IP> <End IP> Scan
-uni <Start IP> <End IP> Scan
-webdav <Start IP> <End IP> Scan
-mdac <Start IP> <End IP> Scan
-media <Start IP> <End IP> Scan
-Frontpage <Start IP> <End IP> Scan
-codered <Start IP> <End IP> Scan
-ftp <Start IP> <End IP> [-ad
-um <IP addr> [Web path] <Message> Mod

Example: scan -webdav 192.168.0.1 192.168.0.255

-Credits DOH?

Note:
- Scan [x] Threads automatically logs all results to scan.txt (no > log.txt needed)
- scan.txt won't be overwritten at your next scan, new results will be appended
- Somehow it always say "Error!" like you can see above, but it works without problems!

think and hope you'll like it

subcorner

May 25 2004, 09:57 PM

good job man, really good idea to put them both

BuzzDee

May 25 2004, 10:20 PM

tried it. scanning with 5000 threads isnt faster than scanning with 1000 threads. so it doesnt really seem to work for higher thread counts.... :/

vnet576

May 25 2004, 10:43 PM

Windows has a built in limit of 4096 I believe. Something to do with memory allocation I believe..not sure.

Killaloop

May 26 2004, 08:33 AM

5000 threads? scan series doesn't use full socket support (raw sockets) so the max. number of threads is "very" limited because of hardware issues and not the program itself.

normal winsocks are only limited for windows 9.x where default are only 100 sockets. This issue does not occur under Windows NT/2K/XP.
however when you set 5000 threads you only set the maximum number. the real value of threads depend on the hardware. you could be on a 10gbit machine and would scan slower than your 10mbit one because of low memory.

QUOTE

Windows has a built in limit of 4096 I believe. Something to do with memory allocation I believe..not sure.

you mixed it up with the maximum socket buffer size which is default 4096 bytes has nothing todo with the number of sockets (65535 are "possible"). socket buffer size is how much information you can write to one socket. this size can be set with 'setsockopt', needs some loops too... scan[x] for sure is good code
oh and the socket buffersize is the problem with netcat and pasting hudge text

Mrwh!P

May 26 2004, 11:52 AM

big thx for this modded version von the scan.exe,will be very usefull for those users with router.cause of the cache of some routers.....

i´ll give this a try

thx again

mfg Mrwh!P

SecureD

May 26 2004, 12:05 PM

nice job dude will test it!

Uli

May 26 2004, 02:07 PM

nice thanks

vnet576

May 26 2004, 05:28 PM

QUOTE (Killaloop @ May 26 2004, 03:33 AM)

5000 threads? scan series doesn't use full socket support (raw sockets) so the max. number of threads is "very" limited because of hardware issues and not the program itself.

normal winsocks are only limited for windows 9.x where default are only 100 sockets. This issue does not occur under Windows NT/2K/XP.
however when you set 5000 threads you only set the maximum number. the real value of threads depend on the hardware. you could be on a 10gbit machine and would scan slower than your 10mbit one because of low memory.

QUOTE

Windows has a built in limit of 4096 I believe. Something to do with memory allocation I believe..not sure.

you mixed it up with the maximum socket buffer size which is default 4096 bytes has nothing todo with the number of sockets (65535 are "possible"). socket buffer size is how much information you can write to one socket. this size can be set with 'setsockopt', needs some loops too... scan[x] for sure is good code
oh and the socket buffersize is the problem with netcat and pasting hudge text

Thanks for correcting me killaloop. I remember reading about the 4096 number before in relation to sockets...but mixed it up.

robsonbr

May 27 2004, 11:51 PM

appears good one, gonna check it out... tnkx m8

bah

May 28 2004, 07:21 AM

Thanks for the tool,

However A useful addition to it would be to scan for specific ports rather than
a range of ports only eg

-p <Port|Port-Port> <IP|IP-IP> Scan port

port-port is only a port range eg 200-9000

is possible for u to modify the tool to scan for a discrete port numbers
eg
port,port-port

21,80,100-400

I think a lot more people would find this very useful.

Miserly

May 28 2004, 07:53 AM

it's not modified by me!

further it's at least possible to scan a special port e.g. simply enter
-p 21
for port 21.
simply make a batch file, should solve your problem