Set computer accounts as owned in bloodhound if local admin privs

[NeffIsBack]

If you achieve to gain local admin privileges you basically have control over the comuter account. Therefore this is account is set to owned in bloodhound now. (Even with NetBIOS name support for the domain 😁)

FYI: this is branched of #35 so it is already up-to-date if this one gets merged

[NeffIsBack]

We could probably delete the bh_owned module now

[Marshall-Hallenbeck]

I'm not sure if it's just me, but setting the bloodhound flag in every protocol seems pretty bad and unmanageable. Is there anyway we could move it to a centralized place?

[NeffIsBack]

Agreed. When you look into these functions the whole block of code mostly the same across the protocols. I just added it to the end of the block but we should centralise a lot of the code probably, but I didn't want to do it in this PR. It is probably a bigger problem.

I can do it in this PR but we should imo open up another one where we tackle the big problem on its own.

[Marshall-Hallenbeck]

Created #96 for us to look into and fix it at a later time.

[mpgn]

With local auth

Bug found

[NeffIsBack]

Showcasing the use case when the domain was not found in the database (e.g. the user specified a wrong domain or used local auth):

1. For Administrator multiple User Accounts were found in the db so we exit. (Forest with several "Administrator" Accounts)
2. For the computer CASTELBLACK we successfully retrieve the account (even without a domain) and set it as owned.

(Final result of course without debug output)

[NeffIsBack]

Working example with --local-auth only adding the host to the database:

[mpgn]

[Marshall-Hallenbeck]

Code looks good but I haven't ran tests since I haven't set up Bloodhound yet. If you've confirmed it works then it should be good to go.