Quote:No my plan is to add real markov, not pseudo-markov. We maybe have a misunderstand here?
Ahh, probably !! I am a bit stupid, so I am probably using the wrong terminology most of the time, sorry.
Quote:Only for old Thompson routers. And they have been fixed in the meanwhile (while its known there is a new attack possible). So its not that efficient.
I understand what you mean here especially in the context of this thread but there are also other routers which have a fairly predictable password. SKY for example use only uppercase alpha 8 characters in length. If you could provide hashcat users with the functionality I was meaning with the term “pseudo-markov†then we could reduce cracking time as a user could restrict multiple occurrences of a given character side by side.
AAAAAADH is unlikely to be a random password so the user could tell the new function to limit the occurrence of a given character side by side to 1. I appreciate this will require a lot of thinking to work out. I wonder if others could contribute ideas or code to help your work load ?
Other BT routers and some Virgin ones have similar predictable patterns which could be exploited using this "occurrence of unique character" feature.
Looking forward to getting some beta testing done today, thank you very much for implementing some of my other requests ! ... You must dread my posts !
Thanks.
@ ZerXes
ZerXes did you understand what atom wrote ? Have you managed to get it to work mostly how you wanted ?