Failed to load the configuration file. Procedure

[TGRBirdFlying]

when i run ./amass intel -addr ip, I found the default configuration file loaded in the path ~/config/amass, Generate amass.log from it, The error is as follows:

07:04:06.742119 BinaryEdge: check callback failed for the configuration 07:04:06.758364 IPdata: check callback failed for the configuration 07:04:06.758525 IPinfo: check callback failed for the configuration 07:04:06.758578 IntelX: check callback failed for the configuration 07:04:06.758660 Netlas: check callback failed for the configuration 07:04:06.758705 ONYPHE: check callback failed for the configuration 07:04:06.758774 PassiveTotal: check callback failed for the configuration 07:04:06.758884 Pastebin: check callback failed for the configuration 07:04:06.758921 PentestTools: check callback failed for the configuration 07:04:06.758948 PublicWWW: check callback failed for the configuration 07:04:06.759009 Quake: check callback failed for the configuration 07:04:06.761376 Ahrefs: check callback failed for the configuration 07:04:06.761965 DNSlytics: check callback failed for the configuration 07:04:06.762003 BufferOver: check callback failed for the configuration 07:04:06.762014 Deepinfo: check callback failed for the configuration 07:04:06.762155 Detectify: check callback failed for the configuration 07:04:06.762189 CIRCL: check callback failed for the configuration 07:04:06.762252 Censys: check callback failed for the configuration

In ~/config/amass there are placed configuration files config.yaml and datasources.yaml as follows:

scope: domains: # domain names to be in scope

• "facebook.com" ips: # IP addresses to be in scope, multiple methods of inserting ip addresses can be used

• asns: # ASNs that are to be in scope

• cidrs: # CIDR ranges that are to be in scope

• "" ports: # ports to be used when actively reaching a service
• 80
• 443
• 8080 blacklist: # subdomains to be blacklisted
• example.example1.com options: resolvers:
• "../examples/resolvers.txt" # array of 1 path or multiple IPs to use as a resolver datasources: "./datasources.yaml" # the file path that will point to the data source configuration wordlist: # global wordlist(s) to uses
• "/root/webtools/domain_tools/domain_dict/best-dns-wordlist.txt" database: "postgres://postgres:post@localhost:5432/amass?testing=works" # databases URI to be used when adding entries bruteforce: # specific option to use when brute forcing is needed enabled: true wordlists: # wordlist(s) to use that are specific to brute forcing
  • "/root/webtools/domain_tools/domain_dict/best-dns-wordlist.txt" alterations: # specific option to use when brute forcing is needed enabled: true wordlists: # wordlist(s) to use that are specific to alterations
  • "/root/webtools/domain_tools/amass/wordlists/subdomain.txt"

datasources:

• name: 360PassiveDNS ttl: 3600 creds: account: apikey: null
• name: ASNLookup creds: account: apikey: 7535310003mshf55573697c52fde2b
• name: Ahrefs ttl: 4320 creds: account: apikey: null
• name: AlienVault creds: account: apikey: ea674a59a5fe9089fdb2078eb66613ebc5e4b497f

I don't know what happend, I hope someone can answer that question. Good luck! another, when I run ./amass enum -list results as follows:

Data Source | Type | Available

360PassiveDNS api
ASNLookup api
AbuseIPDB scrape Active Crawl crawl Active DNS dns Ahrefs api
AlienVault api Alterations alt AnubisDB api Arquivo archive Ask scrape AskDNS scrape BGPTools misc BGPView api Baidu scrape BeVigil api
BigDataCloud api
BinaryEdge api
Bing scrape Brute Forcing brute BufferOver api
BuiltWith api
C99 api
CIRCL api
Censys cert
CertCentral cert
CertSpotter cert Chaos api
CommonCrawl crawl Crtsh cert DNS SRV dns DNSDB api
DNSDumpster scrape DNSHistory scrape DNSRepo api
DNSSpy scrape DNSlytics api
Deepinfo api
Detectify api
Digitorus cert DuckDuckGo scrape FOFA api
FacebookCT cert
FullHunt api
Gists scrape GitHub api
GitLab api
Google scrape GrepApp api Greynoise api HAW archive HackerOne scrape HackerTarget api Hunter api
HyperStat scrape IPdata api
IPinfo api
IntelX api
LeakIX api Maltiverse api Mnemonic api Netlas api
ONYPHE api
PKey scrape PassiveTotal api
Pastebin api
PentestTools api
PublicWWW crawl
Pulsedive api Quake api
RapidDNS scrape Reverse DNS dns Riddler scrape SOCRadar api
Searchcode api Searx scrape SecurityTrails api
ShadowServer misc Shodan api
SiteDossier scrape Spamhaus api
SpyOnWeb scrape SubdomainCenter api Sublist3rAPI api Synapsint scrape TeamCymru misc ThreatBook api
ThreatMiner api UKWebArchive archive URLScan api VirusTotal api
Wayback archive WhoisXMLAPI api
Yahoo scrape * Yandex api
ZETAlytics api
ZoomEye api

[caffix]

What you're experiencing are not errors. It's simply for awareness to help understand which data source integrations are receiving the credentials needed to operate correctly

[mastercho]

What you're experiencing are not errors. It's simply for awareness to help understand which data source integrations are receiving the credentials needed to operate correctly

so you mean failed keyword is not actually failed?

[brutexploiter]

Same issue