That’s fantastic atom thank you for your post.
I understand the limitations of markov but I only used the name markov after a discussion I had with you some time ago. This is why I call it pseudo markov.
In my original feature request I didn’t know how to describe / name it so I borrowed your markov comment. What I was originally asking for is a way to be able to narrow down the key-space if the attacker knows something about the password format, like in ZerXes example.
I would be very grateful if you could let us know how better to describe it for the request page. If the term pseudo markov is misleading could you please suggest another more accurate one and I will change the wiki.
Allowing hashcat users to be able to reduce the brute force key-space in this way would significantly damage the resistance of WPA against even humble cracking machines.
These last two "conditions" listed here...
...would be very useful. I understand there is no way around them at the moment but they would be very powerful.
Thanks.
Quote:you can not do it yet. however, you could not do it with markov either...
I understand the limitations of markov but I only used the name markov after a discussion I had with you some time ago. This is why I call it pseudo markov.
In my original feature request I didn’t know how to describe / name it so I borrowed your markov comment. What I was originally asking for is a way to be able to narrow down the key-space if the attacker knows something about the password format, like in ZerXes example.
I would be very grateful if you could let us know how better to describe it for the request page. If the term pseudo markov is misleading could you please suggest another more accurate one and I will change the wiki.
Allowing hashcat users to be able to reduce the brute force key-space in this way would significantly damage the resistance of WPA against even humble cracking machines.
These last two "conditions" listed here...
Quote:Same letter or digit may only exist twice in same key
At least one letter or digit exist twice in same key
...would be very useful. I understand there is no way around them at the moment but they would be very powerful.
Thanks.