[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <57DC30C2-FBA7-4CD6-A36A-10150F2D44C4@gmail.com>
Date: Mon, 25 May 2015 19:18:33 +0200
From: Marek Wrzosek <marek.wrzosek@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: Using loopback with regex could cause crash
Maybe char=\char if rexgen will accept it that way. But there is (or was) bug in john that caused adding anything after \0 one character to early. If last character of buf is ] than it's easy to repair it ad hoc on command line but otherwise it'll break the regex.
Dnia 25 maja 2015 19:03:29 CEST, Frank Dittrich <frank.dittrich@...lbox.org> napisał(a):
>On 05/25/2015 06:38 PM, Marek Wrzosek wrote:
>> Hi
>>
>> If john.pot contains e.g. "." and john is started with --loopback
>> --rules=none --regex=case=alpha:case="\0" (--regex="\0" doesn't crash
>> with the same john.pot) then this could happen:
>>
>> buf=[sS][eE][xX][iI][sS]
>> buf=0
>> buf=[jJ]
>> buf=[mM]
>> buf=[pP]
>> buf=2
>> buf=9
>> buf=[bB]
>> buf=[cC]
>> buf=[dD]
>> buf=[lL]
>> buf=[gG]
>> buf=[wW]
>> buf=.
>> error: syntax error, unexpected $end
>> Error, invalid regex expression. John exiting now base_word=.
>Regex= .
>>
>> I think that forbidden characters should be escaped with \ or in []
>> brackets, don't you think? First would require changing john, but
>latter
>> maybe only changing regex_alphabets.conf e.g. by adding ".=[.]" line.
>
>I think john's --regex implementation should be changed in a way that
>it
>automatically adds <char>=[<char>] "replacements" for all characters
>that don't have any replacements defined in an alpha section.
>Usually that's what the user would expect, I think.
>
>Frank
--
Marek Wrzosek
marek.wrzosek@...il.com
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
