You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 using sudo 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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: