Open b1k3 opened 1 month ago
Hey @b1k3! π Thanks for flagging this bug! ππ
You're our superhero bug hunter! π¦ΈββοΈπ¦ΈββοΈ Before we suit up to squash this bug, could you please:
π Double-check our documentation: https://rengine.wiki π΅οΈ Make sure it's not a known issue π Provide all the juicy details about this sneaky bug
Once again - thanks for your vigilance! π οΈπ
Is there an existing issue for this?
Current Behavior
When running a scan Harvester is not picking up any API keys configured within the Tool Setting page of the application
Expected Behavior
When configuring the settings for theHarvester within Tool Settings of the GUI and then running a scan it should utilise the API keys provided.
Steps To Reproduce
Environment
Anything else?
When the scan runs and theHarvester is run, it attempts to pick up the api-keys.yaml file from
/root/.theHarvester/api-keys.yaml
as per screenshot below:When connecting to the celery container and checking the file, no keys are saved in this file.
Connecting to the celery docker container
rengine-celery-1
usingsudo docker exec -it rengine-celery-1 /bin/bash
, I located that the file in the below location/usr/src/github/theHarvester/api-keys.yaml
is the file updated by the GUI.As a work around I've copied the
/usr/src/github/theHarvester/api-keys.yaml
to the one in the/root/.theHarvester/
location.