search

owasp-amass / amass

In-depth attack surface mapping and asset discovery
https://owasp.org/www-project-amass/
Other
11.51k stars 1.84k forks source link

unmarshal error #1018

Closed rext49612 closed 3 months ago

rext49612 commented 4 months ago

1008 ERROR OUTPUT with ini format

Failed to load the configuration file: error mapping configuration settings to internal values: yaml: unmarshal errors: line 32: cannot unmarshal !!seq into config.Config

datasource.yaml ERROR

Unable to read the context after specifying with -config flag , tried in docker still unable to read the file even filetype too.

literally no way to specify config file

Need attention

Regards @rext49612

prasgop commented 3 months ago

similar error: Failed to load the configuration file: error mapping configuration settings to internal values: yaml: line 23: did not find expected key

The-Inceptions commented 3 months ago

@prasgop @rext49612 can you provide your configuration file? and what version of amass are you running?

prasgop commented 3 months ago

version 4.2.0. It was throwing error when I initially tried to use the example congif.yaml by uncommenting api sources fields after adding respective keys. I later used oam_i2y to create config and datasources.yaml (new files attached) from config.ini, and it worked. config.txt Now, I am able to run amass. Just that it's runtime is kind of unpredictable. And, I am using oam_subs after running amass to get subdomains as a separate list.

The-Inceptions commented 3 months ago

@prasgop as I look into this, I would advise you to redact your API keys in the datasources file.

prasgop commented 3 months ago

oh yes, I should have. I have removed it now as it's anyway not adding any additional info to the context here.

The-Inceptions commented 3 months ago

@rext49612 Would you be willing to provide a redacted version of your datasources.yaml and your config.yaml?