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

bug(tools): Amass, GAU and theHarvester config files not present when updating #263

Closed
3 tasks done
psyray opened this issue Feb 10, 2025 · 1 comment · Fixed by #267
Closed
3 tasks done

bug(tools): Amass, GAU and theHarvester config files not present when updating #263

psyray opened this issue Feb 10, 2025 · 1 comment · Fixed by #267
Assignees
Labels
bug Something isn't working

Comments

@psyray
Copy link
Contributor

psyray commented Feb 10, 2025

Current Behavior

Only when updating from older version with an existing rengine_tool_config volume and if you use prebuilt_images

Config files for those tools are copying in the Dockerfile from reNgine-ng cloned dir to volumes rengine_tool_config

COPY --chown=$USERNAME:$USERNAME ./config/the-harvester-api-keys.yaml /home/$USERNAME/.config/theHarvester/api-keys.yaml
COPY --chown=$USERNAME:$USERNAME ./config/amass.ini /home/$USERNAME/.config/amass.ini
COPY --chown=$USERNAME:$USERNAME ./config/.gau.toml /home/$USERNAME/.config/.gau.toml

It works if you build your own image, because COPY command is triggered during build, but if you use prebuilt_image, the config files are not copied.

And in the tool settings those 3 are empty, and there's no way to save them (500 error)

Image

Image

So, to solve this problem, we should add a check existence in the update.sh of the celery container, and if not present we should copy config files

Expected Behavior

Config files should be present when updating from old reNgine-ng version prior to 2.1.0

Steps To Reproduce

  1. Clone reNgine-ng 2.0.7 tag
  2. Set .env & run install.sh
  3. Check in the tools settings section there is no config for amass, gau & theharvester
  4. Follow the upgrade process of the wiki
  5. Check on the tools config, the 3 above conf should be empty and 500 error should come

Environment

- reNgine: 2.1.0
- OS: Debian 12
- Python: 3.10
- Docker Engine: 
- Docker Compose: 
- Browser:

Anything else?

No response

Acknowledgements

  • This issue is not a duplicate of an existing bug report.
  • I have chosen an appropriate title.
  • All requested information has been provided properly.
@psyray psyray added the bug Something isn't working label Feb 10, 2025
@psyray psyray added this to the v2.1.1 release milestone Feb 10, 2025
@psyray psyray self-assigned this Feb 10, 2025
@psyray psyray linked a pull request Feb 14, 2025 that will close this issue
Copy link

This issue is being closed because the related PR has been merged into a release branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant