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

Issue: Error Printing Subdomains After Running Amass Command #9

Open
cupello opened this issue Sep 7, 2024 · 1 comment · May be fixed by owasp-amass/config#11
Open

Issue: Error Printing Subdomains After Running Amass Command #9

cupello opened this issue Sep 7, 2024 · 1 comment · May be fixed by owasp-amass/config#11

Comments

@cupello
Copy link

cupello commented Sep 7, 2024

Hi!
After successfully running the amass command, I encounter an error when trying to print the found subdomains to the screen. It seems that the -dir flag is being ignored, and I am receiving the error: dial error: dial tcp 127.0.0.1:5432: connect: connection refused.

IMG_20240907_150916_841
IMG_20240907_150919_578

@cupello
Copy link
Author

cupello commented Sep 9, 2024

Hi! The issue seems to occur because the LoadSettings method is always called, which in turn calls the loadDatabaseSettings method. If there is no database configuration in config.yaml, it will always call the LoadDatabaseEnvSettings method, which will then create a database configuration for PostgreSQL set as primary. As a result, when the LocalDatabaseSettingsmethod is called, there is already a primary database in cfg.GraphDBs, causing the local database to be set as non-primary.

image

image

image

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

Successfully merging a pull request may close this issue.

1 participant