Ron/fuzz-garbage script

[mike <dmciscobgp () hotmail com>]

Ron

 

not sure if this is a windows thing or not. i noticed the output after i tested it and i set the args value for 
"stopafter" to just 10 bytes. the output from nmap reports this as "10 bytes sent" howver i noticed that what was sent 
to the socket in testing was the 1024 bytes default value. seting the chunksize is apparently the only way i can 
control the bytes to be the exact value that nmap reports back as what was sent

 

All

 

did anyone decide to investigate and possibly clean up the script error/tail call() debug messages i reported last 
time. i beleive i mentioned 3 or 4 that had them

 

i was also curious about another topic. using source port 0 for scanning. i remember years back when using nmap, one 
could use the source port as 0/zero, even though that is not considered a port. i liked the fact you could scan a 
target that most people with IDSs and firewalls that worked by filtering through source/dest sometimes could not 
handle. did this option/ability get thrown out due to recent socket limitations on windows or was it the pcap upgrades 
that broke it?

 

thank you

m|ke
                                          
_________________________________________________________________
Find the right PC with Windows 7 and Windows Live. 
http://www.microsoft.com/Windows/pc-scout/laptop-set-criteria.aspx?cbid=wl&filt=200,2400,10,19,1,3,1,7,50,650,2,12,0,1000&cat=1,2,3,4,5,6&brands=5,6,7,8,9,10,11,12,13,14,15,16&addf=4,5,9&ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_evergreen2:112009
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/