Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <003a01cc0a9c$d1449350$73cdb9f0$@net>
Date: Wed, 4 May 2011 16:49:52 -0400
From: "Robert Harris" <rs904c@...scape.net>
To: <john-users@...ts.openwall.com>
Subject: Following all the patch activity, not uploading to the wiki, which patches play well together, revising the wiki page to be better

John-Users,

 

I'm finding it more and more difficult to follow all the patch activity we
have had lately!   Some but not all patches are posted on the patch's wiki
page and some patches don't work well with others.   Some patches are
updated to the next version, and the wiki page may reflects this,  but if
you aren't paying close attention you'll miss it.

 

I like to build the "latest" version of John with all the patches possible,
but figuring out all the latest patches that play well together has been
tough lately.   Because of other builds I can tell that there are two tracks
of OpenMP revision 7 and 4 and the description helps, but that is a little
confusing.  

 

Here is an example of the type of things that should be clear on the page,
but aren't.

Can we apply patch "john-1.7.7-jumbo-1-ssh-06-OpenMP.diff", before or after
the OpenMP revision 4 and/or 7?   Or at all?

 

I attempted to build the following, the other day, and it failed.  (All the
patches took, with some manual adjustments).  The other day, I  considered
this as the "latest version", that has changed a little since

 

These patches all applied after some manual edits, but the build of this
failed, at least on windows.

 

   john-1.7.7.tar.gz with the patches:

                john-1.7.7-jumbo-1.diff

                john-1.7.7-jumbo-1-rar-01.diff

                john-1.7.7-jumbo-1-ssh-06-OpenMP.diff

                john-1.7.7-jumbo-1-utf8-1.diff

                john-1.7.7-SybaseASE-01.diff

 

I think the current patch's wiki page needs to be revised.  I think a
starting list might be to include additional columns such as "modified
date", "OS patch applies to" , etc.   Others?

 

I think the different multi-CPU branches we have is a little confusing,
especially when we mix all those different trees of patches with the
"normal" patches.  That is why I suggested before that we break out those
patches into at least on other separate table.  But, Alex axed that idea.

 

Please chime in on how to what you all think of the patches page, and
possible ways of making it better.

 

-Robert B. Harris from VA

 

 


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.