Reputation
4,054
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
7 23
Newest
 Good Answer
Impact
~307k people reached

Feb
1
reviewed Approve PCI Compliance Scan Failing for supporting TLS 1.0, but removing support breaks < IE 10
Jan
23
comment nmap SYN scan taking forever
Possibly this bug in libpcap and Linux: github.com/nmap/nmap/issues/34
Jan
22
comment what does Pn options stands for in nmap
Yes, this is the intention. In 2010, the old -PN and -P0 names were replaced with -Pn, and -sP was replaced by -sn. This is so that the mnemonic for n means "don't do this." So -n means "don't do name resolution," -Pn means "don't do host discovery," and -sn means "don't do a port scan."
Jan
22
comment Nmap http-brute - Supplying arguments for bruting via GET
@mk444 Either switch to using onsuccess or edit the script to use your real username instead of the random one. Ask more in #nmap on freenode or dev@nmap.org, since stackexchange is complaining about a long comment chain.
Jan
22
comment Nmap http-brute - Supplying arguments for bruting via GET
@mk444 See the script args documented, especially for unpwdb library. Put just the username you want in a file and specify that file with the userdb script arg.
Jan
21
comment Nmap http-brute - Supplying arguments for bruting via GET
@mk444 The script first tries with bogus random creds to see if the failure detection works. If it can't successfully detect failure, it gives up.
Jan
21
comment Nmap http-brute - Supplying arguments for bruting via GET
@mk444 try --script-trace to see the http traffic and make sure it's what you expect. There may be a redirect you need to look for instead of the text on the page.
Jan
19
answered NMap Showing Unknown Private IPs
Jan
19
answered Nmap http-brute - Supplying arguments for bruting via GET
Jan
7
awarded  Good Answer
Jan
6
awarded  Nice Answer
Jan
6
comment Teaching “Secure by Design”
@PiyushSaurabh This looks like the new page: microsoft.com/en-us/SDL/adopt/eop.aspx
Jan
5
answered Teaching “Secure by Design”
Dec
20
comment Nmap NSE Password Brute Force is Stopping on First Positive Instance
It shouldn't be doing that. Are you using Nmap 7.01? telnet-brute got an overhaul recently. If so, we can take a look at your logs with -d3 --script-trace to determine the reason. #nmap on freenode IRC or dev@nmap.org
Dec
19
comment Nmap NSE Password Brute Force is Stopping on First Positive Instance
Also want to point out: --script-args-file is a handy way to deal with long or complicated arguments, especially since it removes the need to quote stuff for the shell and lets you use newlines instead of commas to separate args.
Dec
19
comment Nmap NSE Password Brute Force is Stopping on First Positive Instance
Thanks for pointing this out. Fixed the documentation in r35530, should propagate to the web docs shortly.
Dec
8
comment Resuming an interrupted nmap scan:
@tjt263 Don't scan over WiFi if you can avoid it. There is a lot of interference in this spectrum, so packet loss is a real issue. Even microwave ovens emit at this frequency. If you're going to do a long scan, take the time to set up a good wired connection.
Dec
7
comment Resuming an interrupted nmap scan:
@tjt263 I see your problem. I was assuming it was only your connection to the scanner that was flaky, not the scanner's own connection. No, tmux will not help in that case. Just have to try to make your connection better.
Dec
6
comment Resuming an interrupted nmap scan:
@tjt263 I always use -oA because then I can process output with my eyes (Normal), awk/grep (Grepable), or more advanced tools (XML). Using screen or tmux means your session keeps going when you lose connection. You just reconnect to it (screen -R, tmux attach). There are lots of other useful features, too, but this is one of the best.
Dec
4
answered Resuming an interrupted nmap scan: