-
Notifications
You must be signed in to change notification settings - Fork 173
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
Sharphound block on object #106
Comments
same here, hang indefinitevely on certain domain |
We did identify this issue recently, the problem appears to be in session collection. Theres an unknown edge case where we send API calls to computers and the API calls hang indefinitely. We'll be introducing a hard timeout on those API calls in an upcoming release to ensure that we deal with this scenario appropriately |
Also running in this issue currently, any supert-dirty path we can implement ourself at the current time? |
I'm still trying to track down the cause of this. I added timeouts to all of the computer API calls, but there appears to be another hang in group processing for some reason. I'm away from my computer currently, but I can compile a test build with the computer API timeout fixes and attach it here tomorrow if you want to give it a whirl |
https://github.com/BloodHoundAD/SharpHound/releases/tag/v2.5.6 Give this version a try and see if it works |
No more issues with this version, Thanks for the fix ! |
I ran sharphound on a domain and it end up being stuck on object number 492. I have tried collection method all and default but end up with the same thing. I scanned another domain but didn't encounter the problem.
At first, I tried let it run for 5 hours but he was still stuck. Then i started debugging (see steps after).
In the end I think i can say it doesn't come from the Active directory and not from the network. At least from what i could understand.
I'm running windows 11 and use sharphound version :
So I first import the module with the following :
Then, i launched the scan with :
And i ended up with :
So I tried to test DNS resolution, LDAP connection,
The text was updated successfully, but these errors were encountered: