Leon Jacobs
Leon Jacobs
Definitely planned, just haven't gotten to it yet.
> Is this feature still in roadmap? I agree that it would be very useful. Yes
Doing some performance profiling in another tool I also found wappalyzergo having an outsized impact, with similar profiling results to this issue. Any chance this can be given a look,...
Command invocation is fine. We don't have much control over how it's handled from a gowitness perspective. The values are passed to the drivers as is. [chromedp](https://github.com/sensepost/gowitness/blob/3.0.5/pkg/runner/drivers/chromedp.go#L85) and [gorod](https://github.com/sensepost/gowitness/blob/3.0.5/pkg/runner/drivers/go-rod.go#L121-L128). Unrelated...
Not without a recompilation. I bumped the deps now, will land in a next release in the future.
I don't. Like I mentioned, this is passed to the driver. It will require deeper digging into the implementation to debug. That said, it does seem to honour it somewhat,...
`-D` flag will surface some debugging info that may help in tracing execution flow. Beyond that you need to start editing source :)
@AiPals please don't post LLM generated content here. The relevant dependency has already been updated and will land in a next release.
From the output you sent it looks like the driver can't talk to the spawned Chrome instance using the devtools proto. I noticed in the failing command you are specifying...
I've been wondering about the implementation here and I think we should instead of asking users to prepare files by adding a suffix for resolver information for each entry, rather...