skelsec

> > [@jsdhasfedssad](https://github.com/jsdhasfedssad) can you either share the dump file itself, or at least the msv dll timestamp? > > Certainly. [Here ](https://limewire.com/d/fTI4Z#bf5Od8c6dc) is the dump. Awesome! it's the same...

I've pushed an update to the main branch, which will (hopefully) work for the newer msv versions as well. Please check if out yourselves and let me know if it...

yeah, that totally makes sense. the `strict` parameter was introduced waaaay back when debugging SMB kerberos auth, but I did not followed up since

There have been multiple issues in the SPN handling of `minikerberos`, haven't the time to track it down currently. The `cifs/[email protected]` SPN looks perfectly valid to me, but it could...

the `get_dn` logic is already implemented in the `sam2dn` and `dn2sam` functions. In regards of the `pwdLastSet` attribute, I'll wait for the discussion in https://github.com/skelsec/msldap/pull/63 to finish, as I'm not...

yeah, no we're not doing that here. removed that decorator as I don't see it backported, and definitely want to support py311

Which windows version are you running this? Also, is this computer domain joined? The IP address beginning with `200` in your screenshot gives me a feeling that these machines are...

This was indeed the case, but there has been 2 other versions since, I just forgot to tag this on github. can you please check the deployment via pip on...

I see what you mean but also: https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-nlmp/a211d894-21bc-4b8b-86ba-b83d0c167b00?redirectedfrom=MSDN#Appendix_A_33

I'm open to suggestions, but don't wanna change the current logic as it's per NTLM docs.