g0ldencybersec/cloudrecon

💫 About Me:

Hack Stuff 🖥️
Code Stuff👨‍💻
Fitness 💪
Kaizen✍️

🌐 Socials:

💻 Tech Stack:

📊 GitHub Stats:

🏆 GitHub Trophies

✍️ Random Dev Quote

---

cloudrecon's Issues

Support for output file in JSON format

While a sqlite3 DB has it's pros, typically the more output formats the merrier. Especially with the advent of the latest release of jq just happening 5 days ago after a 5 year hiatus, it would be great for a -o option with the scrape command to write the data in a JSON file. This would allow for easier post processing in certain use cases and is typically a lot more flexible than a sqlite3 DB.

Error: panic: database is locked

Hello, while runnning the tool like so: time CloudRecon store -i ipv4_merged.txt -p 443 -t 10 -c 50. I encountered this error 14 hours later... For context: ipv4_merged.txt

goroutine 45 [running]:
main.runCloudStore.func1(0x0?)
        /root/go/pkg/mod/github.com/g0ldencybersec/[email protected]/store.go:65 +0x468
created by main.runCloudStore in goroutine 1
        /root/go/pkg/mod/github.com/g0ldencybersec/[email protected]/store.go:49 +0x17e

real    837m40.120s
user    1m50.644s
sys     1m45.807s

There is no debug or verbose mode so I can't provide anymore details besides this, I did encounter the same error with -c 100 which is why I changed it to -c 50 but to no avail it seems.

IPv6 support?

This would be super cool since some clients use IPv6 addresses for public dev environments.

increasing -c value affects reliability of results

Hi Team,
Great work with the tool indeed. so I tried with -c 5000 but it reduced number of results dramatically. can you please look into this? because this task is huge and we have to use full bandwidth and processing power or it will take days to finish.