Conversation
Co-authored-by: ek <ek@drimble.com>
Co-authored-by: ek <ek@drimble.com>
There was a problem hiding this comment.
Bug: Browser Path and Database Location Issues
The gowitness command hardcodes the Chrome browser path to /usr/bin/google-chrome, which can prevent visual reconnaissance from working on systems where Chrome is installed elsewhere or not at all, despite gowitness being able to auto-detect browser paths. Additionally, the gowitness report export command assumes the gowitness.sqlite3 database is located within the screenshots directory, but the gowitness capture command does not explicitly specify the database output path, potentially leading to report generation failures.
main.py#L1180-L1194
Lines 1180 to 1194 in 496cc3f
BugBot free trial expires on July 24, 2025
Learn more in the Cursor dashboard.
Was this report helpful? Give feedback by reacting with 👍 or 👎
|
check license compat; may need a reference @cursoragent look into it |
Co-authored-by: ek <ek@drimble.com>
Co-authored-by: ek <ek@drimble.com>
Co-authored-by: ek <ek@drimble.com>
|
Thanks for the note, since HaxUnit only calls gowitness as an external CLI tool without linking or bundling its code, GPLv3 compatibility isn’t a concern. |
Co-authored-by: ek <ek@drimble.com>
Add
gowitnessfor visual reconnaissance to enhance asset discovery.