Kerberoasting-Attack / NTLM Hash cracking
#4
(08-04-2019, 08:12 PM)royce Wrote: If you know for a fact that it's *truly* 12 random characters... then it's not crackable in a reasonable amount of time.

If you do the math:

https://www.wolframalpha.com/input/?i=(2...2B34)%5E12

... it should be immediately clear why.

Thank you. I see the point, but how do you define "truly" random? I assume passwords generated by a browser password plugin are not truly random. But: how do you crack them, if you won't invest a huge effort? If there is no (easy) way, why would you use passwords with > 16 chars? (e.g. https://malicious.link/post/2017/05-06-2...c-numbers/)

(08-04-2019, 11:08 PM)Mem5 Wrote: Moreoever, why Tesla K80 ? GTX 2080 Ti are about 10x faster.
I'm not kerberos expert but I don't think you can 'extract' NTLM hash from a $krb5tgs hash.
I have > 5k USD free credit with azure for testing purposes :-)
OK, thanks for your feedback!
Reply


Messages In This Thread
RE: Kerberoasting-Attack / NTLM Hash cracking - by SailingTobi - 08-04-2019, 11:51 PM