|
Message-ID: <005901d05240$76fcfbe0$64f6f3a0$@net> Date: Thu, 26 Feb 2015 22:50:01 -0500 From: "Robert Harris" <rs904c@...scape.net> To: <john-users@...ts.openwall.com> Subject: RE: Cygwin builds finally work fine with --fork I'll work on this soon. -----Original Message----- From: magnum [mailto:john.magnum@...hmail.com] Sent: Monday, February 09, 2015 11:59 AM To: john-users@...ts.openwall.com Subject: Re: [john-users] Cygwin builds finally work fine with --fork On 2015-02-08 16:48, Rich Rumble wrote: > On Sun, Feb 8, 2015 at 7:10 AM, magnum <john.magnum@...hmail.com> wrote: >> We seem to have nailed the problem with Cygwin builds using --fork. >> It was a deadlock in file locking (Cygwin bug) and we now use a >> different scheme that works fine. > This is GREAT news! Thanks you guys! >> This applies to bleeding-jumbo on Github as of now. By the way I'm >> not aware of any public binary builds of 1.8.0-jumbo-1, not even an >> unofficial one. Perhaps this is a good time to make some (but using >> this latest code). Any volunteers? > Robert Harris typically does a build every so often, and I see two > under custom builds for 1.8.0-j1 > http://openwall.info/wiki/john/custom-builds (1-10-2015) I'm certainly > going to do a build today! > -rich > After regression testing there were some tweaks and bug fixes. You should probably use at least aa60b8bb. magnum --- This email has been checked for viruses by Avast antivirus software. http://www.avast.com
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.