trietend

We also faced this issue using impacket (see https://github.com/fortra/impacket/issues/1772 and https://github.com/fortra/impacket/pull/1773). Using the upn instead of the sAMAccountName gives better results. The upn used on the creation will be stored...

then it is here i guess https://github.com/skelsec/aardwolf/blob/898d861a09063bfea4b609742a5ce08c4784ae00/setup.py#L75

Wouldn't it be the best to run it for all valid users?

I think you only use "--continue-on-success" if the user context matters and therefore you also want to run it for all users. Some plugins would be e.g. - [whoami](https://github.com/Pennyw0rth/NetExec/blob/main/nxc/modules/whoami.py) -...

> All functionality in netexec and therefore all the modules should not be coded to vary with different user contexts. I can't tell you exactly how KeePass works without looking...

> Which functionality/modules would depend on the users context? So far only spider_plus would come to my mind. At least the ones i mentioned above and as @Marshall-Hallenbeck mentioned [met_inject.py](https://github.com/Pennyw0rth/NetExec/blob/main/nxc/modules/met_inject.py)....

I think we can it this way: #### Case 1 - without --continue-on-success One Task per host with users = ["admin", "user"] passwords = ["admin", "password"] This will stop on...

This PR would run the module, but with the last username/secret combination (valid or not). It would be necessary to reestablish the connection for valid creds, to have a valid...