[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1c626457e86b13223fb36616f2efe267@smtp.hushmail.com>
Date: Mon, 25 May 2015 17:17:48 +0200
From: magnum <john.magnum@...hmail.com>
To: john-users@...ts.openwall.com
Subject: Re: Bleeding jumbo now defaults to UTF-8
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
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.
