-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Bug - Scanning issues after recent merge/ commits #479
Comments
👋 Hi @alph4byt3, |
Weird! Let me try immediately on my older VPS build. But I don't think any changes has happened in scanning part, which would fail this. anyways let me check |
How did you update btw? I assume
right? |
@alph4byt3 I can confirm everything is working as expected. My build was from Aug 16 and updated to the most recent. It is working as expected. |
@alph4byt3 @yogeshojha
original code
|
Hey what's up, I didn't update it. I'm on a VM so I went back to a previous screenshot from a couple of days ago without reNgine installed and reinstalled it from scratch (git clone etc etc) I'm quite busy at the moment so when I get free time later I'll go check on it again for any other things I can find. I saw httpx did update something regarding json output so maybe wapwn above is correct |
…-after-recent-m Fixed #479, httpx input issue
Hi @wapwn Thank you very much for pointing this out! You're awesome 🌟 This has been fixed, tested on the most recent version of HTTPX. If this problem still persists, feel free to raise a new GitHub issue, or we can reopen this. |
Thanks @alph4byt3 for reporting this. |
Issue Description
Scans stop working after subdomain discovery but before probing subdomains for endpoints. It seems to be happening during the HTTPX part of the scan.
Here's a normal vuln scan using the default engine in a newly installed instance.
The build I was using before Thursday 26th was fine and that was the day new changes were committed, today I reinstalled rengine due to a power outage hence why I'm now here.
yes
Technical details
None
The text was updated successfully, but these errors were encountered: