Clément Notin

Results 38 comments of Clément Notin

Very good idea! What I do currently is that I backup the db and delete edges just to see, then restore. But that would be way more convenient!

I see the concerned user in this example: ![image](https://user-images.githubusercontent.com/550823/66334937-4bc3aa00-e93a-11e9-8bb9-31ac3d177609.png) But I don't see which abnormal primary group ID/name it has.

I confirm it's necessary!

FYI this was introduced by 5c8ccbdf49b083311a4ea07c0a8b200724110a59 Which was because: > The ntml.create_ calls return a byte string But this isn't what I observe in debugger, due to: https://github.com/mullender/python-ntlm/blob/14e2243e05c8b671c6eae570d670672c9613e563/python30/ntlm/ntlm.py#L219 https://github.com/mullender/python-ntlm/blob/14e2243e05c8b671c6eae570d670672c9613e563/python30/ntlm/ntlm.py#L337

Also, I have other fixes and improvements for this script. Let me know if you want them, then I will create atomic commits and PRs.

Interesting PR :) Looks like PAC_ATTRIBUTES_INFO is not declared though. Shouldn't it be created like in your other closed PR? https://github.com/gentilkiwi/mimikatz/pull/379/files#diff-ab813c3eae657d6a046ca00057a7a32bf229a161f9f957821468bc195c870f84R32-R40

It compiles and work fine now, even against PacRequestorEnforcement=2

Good catch! I just had this issue...

Thanks for replying to this open discussion! I didn't have a specific method except keystroke injections as I mentioned and you suggested too. Another solution would be to put the...

Definitely not an issue for normal students :) I'm wondering if the "attach" command could catch this specific error and add another message explaining to be more patient?