Open m0uka-Dz opened 1 year ago
If you are looking for just the subdomains after your enumerations, please refer to oam-tools.
The specific tool to use is oam_subs
.
Install oam_subs
by running:
go install -v github.com/owasp-amass/oam-tools/cmd/oam_subs@master
Refer to the User's Guide or the Comprehensive Guide for more information.
hello i don't need show " --> ns_record -->"....etc , i need just urls like old verisons of amass .. thnx you
Same here. It broke my recon process.
Hey @pdelteil @mouka0x @The-Inceptions use the below one liner. it works well
amass enum -d example.com | grep -Eo '([a-zA-Z0-9.-]+\.com) \(FQDN\)' | awk '{print $1}' | anew out.txt
or
amass enum -d example.com | cut -d " " -f 1 | grep -i "example.com" | sort -u
it is taking too long to enumerate subdomains :( its better to use older version of amass
hello i don't need show " --> ns_record -->"....etc , i need just urls like old verisons of amass .. thnx you
Same here. It broke my recon process.
I recommend pinning your version to a 3.x release until you work out the changes
I see that Amass is catching a lot of flack from some users as a result of the significant changes in 4.0
To be fair to the project developers, though, I will point out users should never assume a new major version release of any software will work as a drop-in replacement for the previous version
Please, rollback to oldschool way, this update was totally no sense breaking one of the greatest tools for recon, very useful in the past...
Hey, i also face the same issue i want just urls no other data
Please, rollback to oldschool way, this update was totally no sense breaking one of the greatest tools for recon, very useful in the past...
Because the Amass developers are selfishly unwilling to rearchitect the entire tool around your use case and completely reasonable expectations/demands...
/s
... I have fixed all of your problems
Try this:
$ go install -v github.com/owasp-amass/amass/v3/...@master
Optionally, try:
https://github.com/owasp-amass/amass/releases/tag/v3.23.3
... and choose the appropriate build
You're welcome
Please, rollback to oldschool way, this update was totally no sense breaking one of the greatest tools for recon, very useful in the past...
Because the Amass developers are selfishly unwilling to rearchitect the entire tool around your use case and completely reasonable expectations/demands...
/s
... I have fixed all of your problems
Try this:
$ go install -v github.com/owasp-amass/amass/v3/...@master
Optionally, try:
https://github.com/owasp-amass/amass/releases/tag/v3.23.3
... and choose the appropriate build
You're welcome
Honestly speaking, it's rearchitecting that has been done! how a tool that it's very first basic use case is to just retrieve subdomains and return it to the user, remove that option! why not just leave the most wanted feature like it has been, and develop a new option/feature with the new resolve output thing! I'm really very surprised about this rearchitecture decision!
Please, rollback to oldschool way, this update was totally no sense breaking one of the greatest tools for recon, very useful in the past...
Because the Amass developers are selfishly unwilling to rearchitect the entire tool around your use case and completely reasonable expectations/demands...
/s
... I have fixed all of your problems
Try this:
$ go install -v github.com/owasp-amass/amass/v3/...@master
Optionally, try:
https://github.com/owasp-amass/amass/releases/tag/v3.23.3
... and choose the appropriate build
You're welcome
This is the best solution in my opinion.
so whats the exact command do downlaod v 3.23?
so whats the exact command do downlaod v 3.23?
$ go install -v github.com/owasp-amass/amass/v3/...@master
hello i don't need show " --> ns_record -->"....etc , i need just urls like old verisons of amass .. thnx you