![]() |
|
Message-ID: <e9b801702135779d284d9fdc23534a25@smtp.hushmail.com> Date: Tue, 13 Aug 2013 13:55:09 +0200 From: magnum <john.magnum@...hmail.com> To: john-dev@...ts.openwall.com Subject: Re: Bleeding-jumbo release On 11 Aug, 2013, at 16:53 , magnum <john.magnum@...hmail.com> wrote: > On 8 Aug, 2013, at 23:13 , Solar Designer <solar@...nwall.com> wrote: >> I still hope to release bleeding as 1.8.0-jumbo-1 in not too distant future > > Here's the status as of 0d3eaa1: > > The problematic patches from Sayantan now only exist in the bleeding-mask branch. > > All Bleeding-jumbo issues known to me are listed in https://github.com/magnumripper/JohnTheRipper/issues > > I just fixed a bunch of generic build problems/bugs seen on CommonCrypto systems. A generic build now only fails self-test for Dynamic_1300 (any system) and mscash2 (only CommonCrypto systems). > > Other than that, the only definite release blockers if you ask me are a couple of OpenCL formats that should use a split kernel: pbkdf2-hmac-sha256-opencl and 7z-opencl. Both have kernel durations long enough to reboot my MacBook, and 7z even makes Bull reboot iirc. For a release, we can simply omit those formats, ie. move them to unused directory. So pbkdf2-hmac-sha256-opencl is fixed now, and I just disabled 7z-opencl and moved it to unused. 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.