Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How i can print just urls like old versions of amass #984

Open
m0uka-Dz opened this issue Oct 30, 2023 · 6 comments
Open

How i can print just urls like old versions of amass #984

m0uka-Dz opened this issue Oct 30, 2023 · 6 comments

Comments

@m0uka-Dz
Copy link

hello i don't need show " --> ns_record -->"....etc , i need just urls like old verisons of amass .. thnx you

@The-Inceptions
Copy link
Member

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.

@pdelteil
Copy link

pdelteil commented Nov 4, 2023

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.

@0xPugal
Copy link

0xPugal commented Nov 4, 2023

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

@Bishulu
Copy link

Bishulu commented Nov 9, 2023

it is taking too long to enumerate subdomains :( its better to use older version of amass

@mzpqnxow
Copy link
Contributor

mzpqnxow commented Mar 7, 2024

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

@0xrh0d4m1n
Copy link

Please, rollback to oldschool way, this update was totally no sense breaking one of the greatest tools for recon, very useful in the past...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants