Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <52F3F94F-B881-43F6-8156-37F61DAFF85C@columbus.rr.com>
Date: Tue, 27 Sep 2011 07:44:04 -0400
From: David Jones <jonesd@...umbus.rr.com>
To: john-dev@...ts.openwall.com
Cc: David Jones <jonesd@...umbus.rr.com>
Subject: Re: Some ideas about enhanced self-test


On Sep 27, 2011, at 2:29 AM, magnum wrote:

> I take this on-list from here in case someone wants to chime in. This started as a private discussion about eg. crc-32 and dummy getting significantly inflated benchmark figures from including the null password in self-test. The opposite happens with eg. max-length self-test for NT - it would decrease the benchmark figure.
> 

On first blush, I'd suggest having a field bench_weight whose value reflects the relative frequency that's to be tested during benchmarking.  A zero value is used for edge cases that very rare but need to be included in the self test for completeness.  An 8 character password would be given a higher weight than the 20 character test password if that's relevant to the benchmark.

>>Dave

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.