-
Notifications
You must be signed in to change notification settings - Fork 113
Sharphound starts enumeration then quits #55
Comments
Bump anyone have any insight on how to get this working? We didn't have any issues with the old Bloodhound. |
Looks like you're running into a crash of some kind. Can you run the exe directly if you're using the .ps1? |
Sorry, I forgot to mention I am seeing this error with both the .ps1 and the .exe. They both get to the same point and just die out. They both only seem to enumerate 862 objects. |
I just recently pushed several changes, can you update your ingestor and try it again? |
Unfortunately, I am still seeing the same issue: .\SharpHound.exe --Verbose Edit: Seeing the same for both .ps1 and .exe |
Can you do collection methods individually so we can narrow down which particular method is causing issues? |
I was able to run trusts successfully. I ran session and it appeared that it was going to succeed but I am seeing this: Status: 1119 objects enumerated (+0 0.5564396/s --- Using 47 MB RAM ) Ran with the following flags: |
That happens sometimes, it'll take a while but it'll eventually finish. |
Any ideas on how long it would take to finish? I've let it run for quite some time and it still hasn't finished. Still seeing the above. |
I am running SharpHound as a standard domain user. In the past, we were able to run BloodHound with no issues. I am using the default collection and running it with -verbose. We will get an initial run of 862 objects and it never increases from there all the output continues to show is below:
Initializing BloodHound at 11:40 AM on 2/7/2019
Resolved Collection Methods to Group, LocalGroup, Session, Trusts
Starting Enumeration for [redacted]
Status: 862 objects enumerated (+862 28.73333/s --- Using 90 MB RAM )
Status: 862 objects enumerated (+0 14.36667/s --- Using 90 MB RAM )
Status: 862 objects enumerated (+0 9.577778/s --- Using 47 MB RAM )
I have tried with multiple different options and flags and I cannot seem to get it to work.
The text was updated successfully, but these errors were encountered: