-
Notifications
You must be signed in to change notification settings - Fork 362
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
Gowitness Didn't Run #1267
Comments
It seems because of using proxy, gowitness is not running. |
Hey @TheTechromancer thanks a lot, they said they fixed it, I don't get anymore connection refused in debug.log , however, still don't get any screenshots, is this still a proxy issue? |
Hmm, that's strange. I see the URLs in there at least. Can you run the scan with |
Here you are: |
Based on this it looks like due to the proxy, We really need to replace this tool with something decent. It's hard to tell but there may also be an issue with redirections. There are some pretty long redirect chains here, like http://areaclienti.myaccounting.it/ --> https://areaclienti.myaccounting.it/ --> https://www.areaclienti.myaccounting.it/ --> https://www.areaclienti.myaccounting.it/area-clienti/login/?redirect=https%3A%2F%2Fwww.areaclienti.myaccounting.it%2F. |
The following URLs did pass post-check, so they were processed by gowitness. It's unclear why there were no screenshots for them:
I'd recommend running gowitness manually to see if it spits out any errors: /root/.bbot/tools/gowitness --chrome-path /root/.bbot/tools/chrome-linux/chrome --db-path /root/.bbot/scans/cheeky_snape/gowitness/gowitness.sqlite3 --screenshot-path /root/.bbot/scans/cheeky_snape/gowitness/screenshots --user-agent 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36 Edg/119.0.2151.97' --proxy socks5://14ac7cb2f8d2c:4e90f0e479@91.190.191.94:12324 --resolution-x 1440 --resolution-y 900 file -f - --threads 4 |
You need to pipe the urls into it. |
Seems to be another issue with the proxy. It might be worth trying a basic |
Ah okay. Apparently the issue is that chromium doesn't support socks5 auth: puppeteer/puppeteer#1074 |
Thanks a lot. 🙏 I also tried http auth but didn't work.
So, I guess there is no solution for this. I will run gowitness in separate scan without proxy. |
I'm hoping this will get solved when we replace gowitness with playwright. |
Closing this one. Please follow here #698 for updates on the webscreenshot rewrite. |
Gowitness module didn't run and didn't produce any screenshots.
debug.log
output.json
The text was updated successfully, but these errors were encountered: