Combinator attack missing correct candidate on large wordlist
#3
(03-26-2020, 06:31 PM)philsmd Wrote: I don't think the grep test is a good/valid test.

There could be any other (even non-printable) character within that line and therefore the combined (concatenated) result is different.

You could test it maybe like this:
Code:
grep build2373 left.txt | xxd -p | tr -d '\n'

and
Code:
grep guitar right.txt | xxd -p | tr -d '\n'

the combined hexadecimal output (maybe just stripping the newline characters \n) must be the same as
Code:
echo -n build2373guitar | xxd -p | tr -d '\n'

So what I mean is, even if you think the combination is within the file... you could just have a space or anything similar after the words and the grep will still work, while the combination will be wrong (e.g. "build2373 guitar" instead of "build2373guitar")

BTW: also your -m 22000 --stdout command doesn't make much sense (remember --stdout is a special "mode", you can't combine it with a -m x parameter, -m 2000 = STDOUT internally)

This is a fantastic response.  Helps me learn and troubleshoot at the same time.  I'll check into this.  Thanks!
Reply


Messages In This Thread
RE: Combinator attack missing correct candidate on large wordlist - by antimatterizer - 03-26-2020, 07:54 PM