Date: Sun, 31 Oct 2010 05:35:21 +0300 From: Solar Designer <solar@...nwall.com> To: john-users@...ts.openwall.com Subject: custom builds Robert, Erik, all - I finally got around to propagating the custom builds that were initially uploaded to: http://openwall.info/wiki/john/custom-builds to the following somewhat more official places: http://download.openwall.net/pub/projects/john/contrib/win32/ http://download.openwall.net/pub/projects/john/contrib/macosx/ http://download.openwall.net/pub/projects/john/contrib/linux/ http://download.openwall.net/pub/projects/john/contrib/solaris/ I've created/edited README.txt files in the above directories accordingly. All of this is getting propagated to the many mirrors: http://www.openwall.com/mirrors/ I've added direct download links for the Win32 and Mac OS X builds to: http://www.openwall.com/john/#contrib Finally, here's some feedback on the builds themselves (note: I never ran them, but I looked at the files inside the archives): Robert - I'd be nice to create a single ZIP archive that will include the required cygz.dll file. This will save a line on the JtR homepage. The archive filename can be made shorter. I suggest that instead of john-1.7.6-jumbo-7-netscreen-script-2.04-sha1_gen-1-win32.zip (and the like) you use something like john-1.7.6-jumbo-7-rs904c-1.zip (where "1" will be your own revision number). Then you can have a README.txt file inside the archive, which will explain what patches are included, etc. In the builds for 32-bit x86, the SSE2-enabled build should be made the primary one in some way - perhaps it should be called just "john", whereas the MMX build should be made slightly harder to use inadvertently - I suggest placing it in john-ancient-computer.zip inside the main archive. A plain 386 build is probably no longer needed at all, or you may similarly add it to the extra archive. (Somehow people tend to use 386 and MMX builds not realizing that they should be using SSE2.) This applies to all of: Win32, Linux, Solaris (but use .tar.gz rather than .zip on Linux and Solaris). Robert - it is great that you've renamed the documentation files to have the .txt suffix on Win32, but perhaps it's better not to do that in your Linux and Solaris builds. Robert - JFYI, your full static linking on Linux makes your build require a Linux 2.6+ kernel. This is probably a non-issue for almost all users, though: whoever still runs Linux 2.4 should have no problem building John from source. There's a way to avoid this (I am avoiding it in JtR Pro with hybrid static/dynamic linking), but let's not bother. Erik - your john-1.7.6-jumbo-7-macosx-universal-2.zip extracts to a directory named john-1.7.6-jumbo-7-macosx-universal-1 (not -2), which is a bit confusing. Then, README.macosx says "There's currently no up-to-date documentation." I think this phrase is a remnant from your builds of 1.6.x versions of JtR. The documentation actually looks up to date, and it's updated in jumbo-7 accordingly to that patch's changes. Thank You! Alexander
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.