[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1e0f2b4bd9bc88baedfaa314e9c529b7@smtp.hushmail.com>
Date: Wed, 3 Oct 2012 18:51:00 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: o5logon format hacks
On 3 Oct, 2012, at 18:45 , magnum <john.magnum@...hmail.com> wrote:
> ...here's how I *think* we could do to all non-hash formats in order to get proper dupe detection and no warnings.
>
> 1. Use a short binary size (eg. 4) so we don't waste too much memory.
>
> 2. Write a simple mockup binary() that just returns a 4-byte hash of the full ciphertext. This could be standard crc32 or something else, but it should use all of the ciphertext.
>
> 3. Use standard binary_hash() functions just like the ones you used now.
Small correction: We should probably use 8 bytes and crc64 in order to be reasonably safe against hash collisions.
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.
