sensepost / gowitness

🔍 gowitness - a golang, web screenshot utility using Chrome Headless
GNU General Public License v3.0
2.87k stars 329 forks source link

Support for chromium #68

Closed JDRanpariya closed 3 years ago

JDRanpariya commented 3 years ago

Is your feature request related to a problem? Please describe. I'm miss some screenshots with chrome headless

Describe the solution you'd like I would like if chromium is available for screenshotting the sites.

Describe alternatives you've considered Chromium

Additional context I hope it will be in actions ASAP.

leonjza commented 3 years ago

Im sorry but it is really hard to understand this one. We already use Chrome for screenshots. As for weirdness around screenshots there are a lot of factors, including your network connection and the remote web servers behavior. Without debugging that first it is impossible to do anything.

leonjza commented 3 years ago

If you want to use a specific version/build of Chrome/Chromium, you can use the chrome path flag.

JDRanpariya commented 3 years ago

Ok cool. I also want to ask about screenshotting of sites which do not have valid ssl certificate generally chrome ignores the empty/blank pages. do you have any idea on how to screenshot such pages? ( phantomjs supports screenshotting sites without valid ssl certificate)

Screenshot (102)_LI

Screenshot (103)

so basically even after getting 200 response it's not showing empty. according to my internet connection I had set --thread=2 though around 75% screenshots were like that. also how does gowitness handles redirects?

leonjza commented 3 years ago

gowitness should screenshot sites with invalid certificates just fine. I tested with all of the badssl.com subdomains successfully.

JDRanpariya commented 3 years ago

Then I think might be it's my network or server issue. I would like to close the issue but before that can you tell how does gowitness handles the redirects? Thanks for good conversation bruh.

leonjza commented 3 years ago

It follows them.