Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 22 Jun 2011 20:10:48 -0500
From: "JimF" <jfoug@....net>
To: <john-dev@...ts.openwall.com>
Subject: Re: 1.7.8.Jumbo-1


From: "Solar Designer"
>> It may be a little late in the game to get it into 1.7.8-J1,
>
> No, it's not late.  If you submit a patch today, I'll consider it for
> inclusion in -jumbo-1 tomorrow.

I will try to get the code, and get a patch up.  Like I said, the machine is 
not here at home, and I am actually out at my cabin site right now. However, 
I should be able to remote in later tonight when I get home.  I will do what 
i can to get the patch in.

>> Alex, what are your plans for J1?  Is J1 going to be just a simple port 
>> of
>> J6, and then we get the recent patches in (and this request), into a 
>> quick
>> J2 follow up?  Or do we try to get these recent changes into a port of 
>> the
>> J6 code?
>
> In general, my intent is for -jumbo-1's to be straightforward ports of
> the latest jumbo from the previous JtR release, but with obvious problem
> fixes added.  So patches that fix bugs/problems are within consideration
> for -jumbo-1, whereas patches that make invasive changes or add features
> are to be postponed for -jumbo-2.

Ok.  The make file change 'should' be non-invasive.  It would have those 
formats built by default, but provides a quick method to disable them on 
systems with problems.  I know that magnum did some work, using opensslv.h 
and #defining versions.  This code causes proper compiling on a system of 
mine, but the link fails.   Thus, in theory, it looks good, but there are 
systems where compile time detection may not be the best.  AFAIK, on that 
system, openssl is not properly installed.  However, I have no control over 
that, so I end up having to do a lot of hand editing (currently).

There were several patches which were bug fixes.  There is also mscash2, 
which magnum and I are still working on.  I might try to get a single patch 
done, with all of the tested fixes in it.  There may still be some 
optimizations coming, but that is obviously not as important as getting 
things working fully and properly.

Jim. 

Powered by blists - more mailing lists

Your e-mail address:

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