Conversation
|
@Schamper, as far as I know, this is complete. I would love for this to be merged as quickly as possible so I can work on the BloodHound PR more comfortably |
|
After further testing on the Bloodhound plugin, I’ve noticed a few missing fields. While these need to be addressed, I’d prefer to merge the current PR now and handle those specific fixes directly within the Bloodhound PR. |
What would those be? |
Adding some fields in the records that I discover as look at each bloodhound Json |
|
Wouldn't it be nicer to just add those in this PR? Especially if it's just a few fields. |
I totally see your point, and normally I’d agree. The main issue is that bouncing between these two PRs is getting a bit messy since they depend on each other. That said, if you’d prefer to have everything polished in one go before merging, I’m happy to hunker down and finish the fields here. |
|
I don't see any changes to the existing records in #1598, so all of the proposed improvements are already in this PR? |
I've actually moved the changes regarding the record enhancement from #1598 into this PR. I'm currently adding a few more updates on top of those, and I'll push everything once it's ready for review. |
This PR expands the parser's coverage by adding support for several new record types, ensuring a more comprehensive map of the target environment.
Also, added better handling in case the pek cannot be unlocked