[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <05bb310d4801ab3929a542caddc85bbe@smtp.hushmail.com>
Date: Fri, 13 Apr 2012 00:04:22 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: MSCash2 formats reliability & usability
On 04/12/2012 11:03 AM, magnum wrote:
> On 04/12/2012 12:17 AM, Solar Designer wrote:
>> Yet another issue is that strings of the form something#32hexdigits are
>> valid for "hmac-md5", so that's what the above ones are autodetected as.
>> Perhaps we want to have mscash and mscash2 (as well as their CUDA and
>> OpenCL varieties) checked before hmac-md5. Maybe we should rename
>> hmacMD5_fmt_plug.c into non-plug and register it explicitly after other
>> stuff. For consistency, maybe we should do it for hmacSHA1_fmt_plug.c
>> as well. SHA-2 based HMACs are already non-plugins for another reason.
>
> I'll have a look at this.
Fixed as suggested.
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.
