c3c
c3c
Oh and really cool idea to have LDIF support! Now we just need the other way around… snapshot to LDIF to an external LDAP server and then run tooling (bloodhound/pingcastle/etc)...
Hi and thanks for the kind words! I had to read over the code first to see what exactly is going on: indeed, only the 'member' attribute is parsed for...
AD Explorer snapshots collect information from a single DC (and domain) only, so the information we get is limited. You could run additional snapshots against different DCs of linked domains...
In that case, probably something that changed in the data format that BloodHound expects vs. what we output in the JSON file currently.
closing assuming this is fixed :)
+1 i would like to use this library for parsing large sql dump files
Got the same error, any workaround?
Thanks for implementing this! Is this a fully-compatible LDIF format or does bofhound have its own format? (E.g. I'm not sure the normal LDIF format has dashes in between lines:...
Thanks for explaining! I think it would be better then to modify the PR for it to say output mode "BOFHound" ?
Sure, could you PR it? Alternatively, I'm also happy to merge in the two different modes.