search

codingo / Reconnoitre

A security tool for multithreaded information gathering and service enumeration whilst building directory structures to store results, along with writing out recommendations for further testing.
GNU General Public License v3.0
2.1k stars 457 forks source link

Using dir command with gobuster #113

Closed Anon-Exploiter closed 4 years ago

Anon-Exploiter commented 5 years ago

The latest version of gobuster won't work without specifying dir before performing directory brute-forcing. Added dir in it.

Before: gobuster -w dict.txt -u http://$ip:$port/ -s '200,204,301,302,307,403,500' -e

After: gobuster dir -w dict.txt -u http://$ip:$port/ -s '200,204,301,307,403,500' -e

Anon-Exploiter commented 5 years ago

Also, in case the pull request gets accepted, also edit the readme file of the repository, with updated output because why not? ¯\(ツ)/¯

Preferably run against metasploitable(2/3) because it'll show many things about Reconnoitre!

codingo commented 5 years ago

I'll need to review the new student VM but this has intentionally been held back previously as the offsec VM didn't yet support gobuster 2.x (which has this functionality change). I'll review soon and then merge if appropriate.

codingo commented 4 years ago

Closing this for now. This change will be made once the student VM supports gobuster 2.x as a default.

Anon-Exploiter commented 4 years ago

Sure, ^ just FYI, I don't think so everyone uses it for OSCP only, I myself utilize this and nmapAutomator in various client engagements. I'd suggest keeping separate branches for both :)

codingo commented 4 years ago

@Anon-Exploiter although I can appreciate that, I think moving to something like https://github.com/codingo/Interlace makes more sense in a professional setting. I work as a pentester myself (and an active bug bounty hunter) and don't think any of these group scanners are appropriate for that work.