Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 09 Oct 2013 00:00:52 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: 7z valid()

On 2013-10-01 12:36, Solar Designer wrote:
> Dhiru,
>
> On Tue, Oct 01, 2013 at 03:38:48PM +0530, Dhiru Kholia wrote:
>> On 10/01/13 at 01:26pm, Solar Designer wrote:
>>> The 7z format is lacking proper valid().  Can you please implement it?
>>> Please test this little task as higher priority than any other JtR
>>> development.
>>
>> I was hoping to get more functionality (and correctness stuff) in-place
>> before doing this part ;(
>
> ... and I am tempted to start requiring proper valid() before you commit
> the very first revision of a new format. ;-)

7z is nowhere near Dhiru's high score in "bwtdt" from two months ago 
though. I'll spare you the details, although it was so bad I found it 
funny. It did waste some of my time though, again.

Anyway, here's an incomplete list of formats with a valid() similar to 
7z: fde, blackberry-es10, cloudkeychain, eCryptfs, EFS, mssql12, 
blockchain-opencl, encfs-opencl and RAR5.

Maybe I should enable the "valid killer self-test" by default, even 
though it usually segfaults instead of fails with a clue. Heck, I could 
just throw any segfaulting format into unused without further notice, 
for Dhiru to fix. But even that will waste a lot of MY time and not 
Dhiru's. Just as compiling the above list did. And just as opening 10 
GitHub issues will.

magnum

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ