-
Notifications
You must be signed in to change notification settings - Fork 42
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
Bloodhound 4.1 compatibility #29
Conversation
Successfully tested with data collected with the last version of bloodhound.py. Not tested with data collected with SharpHound. |
Hey @WilliamBruneau, thanks for this great PR! With some modifications I'm using it in a project to programmatically ingest BloodHound 4.2 (non-Azure) data and it works really well. I didn't want to open a PR on a PR, but I did want to share my fixes:
|
Hey @y4yan, I believe that error is caused by the typo mentioned in my previous comment under point 1. Perhaps fixing that typo solves your problem as well. |
Hey @chvancooten thanks for your fix ! but I have an other one now :/ sudo bloodhound-import -du neo4j -dp neo4j --database 127.0.0.1 -p 7687 /tmp/json/20221117141902_computers.json ` /tmp/json/20221117141902_computers.json /usr/lib/python3/dist-packages/requests/init.py:89: RequestsDependencyWarning: urllib3 (1.26.10) or chardet (5.0.0) doesn't match a supported version! Traceback (most recent call last): File "/usr/local/bin/bloodhound-import", line 11, in File "/usr/local/lib/python3.8/dist-packages/bloodhound_import-0.0.9-py3.8.egg/bloodhound_import/init.py", line 46, in main File "/usr/local/lib/python3.8/dist-packages/bloodhound_import-0.0.9-py3.8.egg/bloodhound_import/importer.py", line 363, in parse_file File "/usr/local/lib/python3.8/dist-packages/neo4j/_sync/work/session.py", line 437, in write_transaction File "/usr/local/lib/python3.8/dist-packages/neo4j/_sync/work/session.py", line 333, in _run_transaction File "/usr/local/lib/python3.8/dist-packages/bloodhound_import-0.0.9-py3.8.egg/bloodhound_import/importer.py", line 186, in parse_computer EDIT: It seems that I have a workaround by replacing UserId by UserSID. |
Hello guys! After modifying the files as mentioned above, I have a similar issue with @y4yan :
|
@wowter-code Try calling it as a module: |
|
For me, everything works great with the latest master branch and the changes from PR #37 now :) |
No description provided.