|
Message-ID: <49a11c75875752d1aa3ac96581e8cba4@smtp.hushmail.com> Date: Tue, 03 Jul 2012 01:49:10 +0200 From: magnum <john.magnum@...hmail.com> To: john-dev@...ts.openwall.com Subject: Re: plans for 1.7.9-jumbo-7, new formats interface, 1.8 On 2012-07-03 01:08, Solar Designer wrote: > I think that it would be good for us to release a 1.7.9-jumbo-7 with > little more than bugfixes for issues found in -6, in 1-2 weeks from now. We have kept all the hazard stuff in bleeding-jumbo. I think Dhiru added one or two formats. Dhiru, are these safe for old versions of OpenSSL and so on? > Thus, I think that we either need to keep magnum-jumbo conservative for > now (as opposed to bleeding-jumbo) or start a new bugfix-only branch > relative to 1.7.9-jumbo-6. magnum - I'll let you decide on this. We'll just use bleeding for the crazy stuff for now, and start a third branch only if/when needed. Dhiru, please confirm: From now on push to bleeding if you are unsure, or consult the lists. However: - We could consider merging Jim's generic SHA-2 code that is now in bleeding. It's nice and clean and we've seen no problems with it. It would give a whole bunch of new formats to people stuck with OpenSSL 0.9.7. > Moving to new formats interface in a "main" tree (that most of us work > on) is not planned until August (if not later). However, we will need > to make such a move (maybe to some intermediate work-in-progress formats > interface) in July for myrice's work on password generation on GPU > specifically. I am hoping to find time to work with myrice on that. > This is one of my priorities (which I got too many of, unfortunately). > > 1.8 won't be out until at least September. But we might have the > formats interface of 1.8 finalized in August if we try really hard - > mostly if I am able to dedicate enough time to this, as opposed to > other tasks (most of them non-JtR). Sounds all good to me, thanks for clearing this up. 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.