amass not executed when performing subdomain scan

[NightRang3r]

Issue Summary

Hi,

I have noticed that amass is not executed when performing a subdomain scan .

The 'default_subdomain_tools' list contains the value 'amass' where the 'tools" variable contains tools from the yaml file which are 'amass-active' or 'amass-passive'

https://github.com/yogeshojha/rengine/blob/f31e7060dbc2e39442ee6b5f7648fb14137910f6/web/reNgine/tasks.py#L514

https://github.com/yogeshojha/rengine/blob/f31e7060dbc2e39442ee6b5f7648fb14137910f6/web/reNgine/tasks.py#L526

The following if statement will not find 'amass-active' or 'amass-passive' in the 'default_subdomain_tools' list thus it will not execute amass.

https://github.com/yogeshojha/rengine/blob/f31e7060dbc2e39442ee6b5f7648fb14137910f6/web/reNgine/tasks.py#L549

Steps to Reproduce

1. Start docker logs docker logs --follow rengine_celery_1
2. Start a subdomain scan
3. You should notice that amass is not executed

Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?

[github-actions[bot]]

👋 Hi @NightRang3r, Issues is only for reporting a bug/feature request. Please read documentation before raising an issue https://rengine.wiki For very limited support, questions, and discussions, please join reNgine Discord channel: https://discord.gg/azv6fzhNCE Please include all the requested and relevant information when opening a bug report. Improper reports will be closed without any response.

[3ntr0phy]

Can you please fix this issue or modify the wiki ? There is contradictory information and apparently we cannot run amass at all. I had to modify tasks.py with default_subdomain_tolls = [ 'amass-active',' amass-passive',' assetfinder',' sublist3r',' subfinder', oneforall' ], not the best fix

Cheers :)

[0xb33]

I found a temp fix for running both amass-passive and amass-active. it works for me.

Take a look : https://github.com/0xb33/rengine/commit/a6a1f7acab2184a795c2153af1726a89069450e2

Cheers :)

[psyray]

Could you try on v2 and reopen issue if problem persists