[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 25 May 2015 18:12:30 +0200
From: Marek Wrzosek <marek.wrzosek@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: Bleeding jumbo now defaults to UTF-8
W dniu 25.05.2015 o 17:17, magnum pisze:
> On 2015-05-25 14:15, Frank Dittrich wrote:
>> On 05/25/2015 10:32 AM, magnum wrote:
>>> If running with --enc=raw, the warnings will not be emitted and it will
>>> behave just like non-jumbo (at least in this regard). This is actually
>>> just an alias for --enc=ascii but the latter name might be confusing for
>>> this use.
>>
>> --encoding=raw isn't mentioned in doc/ENCODINGS, and raw isn't listed
>> for --list=encodings.
>> s/ASCII/ASCII (or raw)/ in --list=encodings (like it is done for latin1)?
>> Then, bash completion should be able to recognize this encoding.
>
> Maybe we should.
>
>> What other undocumented features are hidden in john?
>
> This is a pure alias for backwards compatibility IIRC, not some
> undocumented feature. I used it now because it made more sense in this
> context.
>
> There may be more such aliases: I think both ansi and latin1 are
> (ambiguous) aliases for ISO-8859-1. It seems the latter is documented.
>
> magnum
>
>
ANSI could be confusing, because MS is calling ANSI CP1252 in Western
Europe, but in Central Europe ANSI means CP1250. Furthermore CP1252 is
superset of ISO-8859-1, but it's not the case with CP1250 and
ISO-8859-2. But polish lower.lst is ASCII, so this is irrelevant. Also I
don't know if anyone is using non-ASCII characters in passwords in CE,
but would be great if polish lower.lst was UTF-8.
In doc/ENCODINGS lacks information how new default affects incremental
mode, but there is only one mode that needs --target-encoding option.
--
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.
