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
{{ message }}
Repository navigation
Add functionality to the output flag to output to a directory #16
Hey hey @SoftAndoWetto !
Thanks for the report. I’ve prepared a fix in #17 and would appreciate validation in the same environment where you originally encountered the error before releasing it.
Could you please test these two forms?
Explicit output file:
-o /home/htb-ac-1565529/Downloads/GhostHound.json
Expected: writes exactly to /home/htb-ac-1565529/Downloads/GhostHound.json
Existing output directory:
-o /home/htb-ac-1565529/Downloads
Expected: writes to /home/htb-ac-1565529/Downloads/ghosthound_output.json
If you have Cargo installed, you can test the PR in isolation with:
It would also help if you could confirm whether the explicit full-file path failed originally, or whether the failing command passed only the directory to -o
Activity
JVBotelho commentedon Aug 9, 2026
Hey hey @SoftAndoWetto !
Thanks for the report. I’ve prepared a fix in #17 and would appreciate validation in the same environment where you originally encountered the error before releasing it.
Could you please test these two forms?
Expected: writes exactly to
/home/htb-ac-1565529/Downloads/GhostHound.jsonExpected: writes to
/home/htb-ac-1565529/Downloads/ghosthound_output.jsonIf you have Cargo installed, you can test the PR in isolation with:
The test binary will be at:
It would also help if you could confirm whether the explicit full-file path failed originally, or whether the failing command passed only the directory to
-o