-active scan problem

[Phoenix1112]

I was using it like this before.

amass enum -active -d example.com -o active_output.txt

but now when i use this command with new version the output does not contain pure subdomains.

example.com (FQDN) --> mx_record --> aspmx3.googlemail.com (FQDN)
example.com (FQDN) --> mx_record --> alt2.aspmx.l.google.com (FQDN)
example.com (FQDN) --> mx_record --> alt1.aspmx.l.google.com (FQDN)
example.com (FQDN) --> mx_record --> aspmx.l.google.com (FQDN)
example.com (FQDN) --> mx_record --> aspmx2.googlemail.com (FQDN)

[caffix]

Correct.

The amass tool launches your intelligence collection / enumeration task and now prints out what's being discovered during this process.

During and after the execution of the task, SQL statements sent directly to the database, or other tools, can extract the data of interest to you.

sqlite3 amass.sqlite "select content->>'name' from assets where type = 'FQDN'"

[Phoenix1112]

So, can we point to the config.ini file with the -config parameter? I want to see the command that I can scan with our api keys.

[caffix]

Amass v3 will accept the ini file, but v4 only accepts the YAML files. Your credentials for data sources are entered into the datasources.yaml file

[Phoenix1112]

I run it using the datasources.yaml file as you said, but I got an output like the one below.

example.com (FQDN) --> mx_record --> aspmx3.googlemail.com (FQDN)
example.com (FQDN) --> mx_record --> alt2.aspmx.l.google.com (FQDN)
example.com (FQDN) --> mx_record --> alt1.aspmx.l.google.com (FQDN)
example.com (FQDN) --> mx_record --> aspmx.l.google.com (FQDN)
example.com (FQDN) --> mx_record --> aspmx2.googlemail.com (FQDN)`

there must be a way to use this program in practice. because I use amass in my automation programs and thousands of people like me use amass for automation. I need a parameter that will output clean.

[caffix]

That output is only for human eyes. The db subcommand currently provides ways to extract the data from the database, and soon we will be releasing the oam_subs tool for this purpose. Check out the following blog post for more help:

https://medium.com/@RISHII_R_MAKHIJA/step-by-step-guide-installing-and-migrating-from-amass-v3-to-v4-on-linux-6fbea84c150d