external graphdbs don't work (mysql,posgres)

[remotejob]

config:

1. var [graphdbs] [graphdbs.postgres] url = "postgres://codeline:codeline@127.0.0.1/amass?sslmode=disable"

2.var [graphdbs] [graphdbs.mysql] url = root:codeline@tcp(127.0.0.1:3306)/amass?timeout=10sec

Both vars don't work, I have no doubt all DB is remotely accessible.

[thapr0digy]

Running into this same issue while trying to set up a postgres one which will be ingested into Neo4j.

[vincentcox]

Any news on this?

[victor-shneer]

the same for me. I run Postgres in docker

[vincentcox]

Unfortunately this bug seems ignored by the team/developers

[victor-shneer]

@vincentcox I'm looking inside tests and see that there is an additional flag that is not mentioned in docs: local_database = false

https://github.com/OWASP/Amass/blob/72765f054259480015925ec0fdbb99d44b358caf/config/graphdb_test.go#L52

It is the first time I read Go so I may be missing something. But I'd try to run it with it

[vincentcox]

Good find! Let us know if that did the trick.

I also ran the database locally from what I can remember. But that shouldn't be an issue

[victor-shneer]

no luck :( with local_database = false everything becomes even worse - no output, and no errors. So it doesn't ignore the flag but it breaks something. Here is the commit from 2022 Feb when the flag was deleted from config example. It has something to do with the "in-memory database". Hope it can help someone who will try to fix the issue. Maybe if install the older version of Amass it will work with external db

[vincentcox]

That's unfortunate! Thanks for checking it

[caffix]

Unfortunately this bug seems ignored by the team/developers

Only ignored because we are currently changing the data model and the database management systems that will be supported in upcoming releases