TheTechromancer
TheTechromancer
``` [WARN] internal.excavate: Error sanitizing event data "https://auth." for type "URL_UNVERIFIED": Invalid URL: "https://auth." ```
This has recently become an issue for us as we are trying to add support for python 3.13.
Fixed in https://github.com/blacklanternsecurity/bbot/pull/1972.
Yes, this is on our TODO list. Our current wappalyzer module is using an out-of-date library, and needs to be updated. Most likely the new wappalyzer will be built on...
Also @CarsonHrusovsky, it's possible the reason you're seeing different results is because wappalyzer is looking at the javascript files, etc. in addition to the main HTTP response. If you want...
If you run wpscan manually on that URL, does it behave okay?
It might make sense to put an `idle_timeout=` on the wpscan command, in case it decides to get stuck again.
Yes that's true. Typically if it's unexpected and needs the user's attention it should be a warning. Otherwise if it's a more common occurrence it should probably be verbose/debug.
Damn shame, this was a nice feature.
This is probably the same bug frontend ran into, where certspotter held up the scan. Most likely a deadlock in httpx, another nail in its coffin.