Skip to content
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

Latest bloodhound compatibility #28

Open
mwgielen opened this issue Nov 23, 2021 · 4 comments
Open

Latest bloodhound compatibility #28

mwgielen opened this issue Nov 23, 2021 · 4 comments

Comments

@mwgielen
Copy link
Contributor

No description provided.

@ravisab
Copy link

ravisab commented May 2, 2022

Hello, are there any plans to update the scripts to make them compatibile with the current available version?

@PatchRequest
Copy link

There are two open Pull requests for it
#30
and
#29
I tested #30 for a few days now. It seemse to work

@ravisab
Copy link

ravisab commented Jul 9, 2022

Using python 3.10.4 64-bit on Windows Server 2022.
I generated collection data using

SharpHound -c DCOnly --NoZip --outputdirectory C:\Bloodhound-Collectors\Temp

This gave me a bunch of json files.
Then I tried uploading them one by one to the database using the files from #30 :

"C:\Program Files\Python310\Scripts\bloodhound-import.exe" -du neo4j -dp MyPassword C:\Bloodhound-Collectors\Temp\20220428154356_containers.json

However I simply get the error below:
<coroutine object main at 0x00000179E771E8F0>
sys:1: RuntimeWarning: coroutine 'main' was never awaited
RuntimeWarning: Enable tracemalloc to get the object allocation traceback

I thought maybe I need Python 2.7, however there is no asyncio==3.4.3 available for Python 2.7

Where am I going wrong?

thanks.

@flyingcloudbunny
Copy link

flyingcloudbunny commented Nov 8, 2022

Am very new to python directory structures and came across the same similar problems due to the following issues:

  1. I already had to official 0.9 released bloodhound-import installed so in init.py

from bloodhound_import import parse_file, add_constraints from bloodhound_import import database

kept references the actually module that is NOT updated with #30's code. Afterward, I adjusted these lines to

from importer import parse_file, add_constraints import database

and in the main.py

from bloodhound_import import main to from __init__ import main

At the path the cloned branch pr is at and into the innermost bloodhound-import directory with the python files, I ran the following:

python __main__.py -du username -dp password [datetime]_containers.json

I'm not sure if this is the conventional way to run such python files, but it served its purpose.

daddycocoaman added a commit to daddycocoaman/bloodhound-import that referenced this issue Dec 14, 2022
daddycocoaman added a commit to daddycocoaman/bloodhound-import that referenced this issue Dec 14, 2022
dirkjanm added a commit that referenced this issue Dec 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants