[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4E74825F.7070608@bredband.net>
Date: Sat, 17 Sep 2011 13:19:59 +0200
From: magnum <rawsmooth@...dband.net>
To: john-dev@...ts.openwall.com
Subject: Re: 1.7.8 Jumbo-6
On 2011-09-17 08:12, Solar Designer wrote:
> Would you summarize the changes since -jumbo-5, please - in a form
> that you feel is suitable for john-users (detailed) and Freshmeat
> (brief). I'll derive other levels of detail (for other places) from
> these two.
Here is a first brief collection of all patch descriptions, for a starter:
* Numerous bug, performance and portability fixes (JimF/magnum)
* New encodings supported: iso-8859-1, iso-8859-15, koi8-r, cp437,
cp850, cp858, cp866, cp737, cp1251, cp1252 (JimF/magnum)
* Full encoding support for single mode, rules and character classes.
Some new character classes added (JimF/magnum)
* Full encoding support for all formats, including md5_gen (JimF/magnum)
* Unicode DumbForce external modes added (magnum)
* User-defined character classes added (magnum)
* Tripcode format added (Solar)
* DMD format fixed to behave like normal formats (magnum)
* Generic-crypt format now recognises some subformats
(md5/sha256/sha512) for benchmarking (magnum)
* Wordlist mode is now much faster when using memory buffer (JimF/magnum)
* New option bools in john.conf: LogCrackedPasswords, AlwaysReportUTF8,
UnicodeStoreUTF8, CPstoreUTF8 (magnum)
* Pkzip format added (JimF)
* raw-md5-unicode replaced with faster 'thin' raw-md5u (magnum)
* Added the ability for john.conf file to include other .conf files,
sections including sections [eg. rules including rules] (JimF)
* Duplicated rules supressed (JimF)
* New rule reject flag ->N (reject unless length N is supported by
format) (magnum)
> Also, what systems did you test "j6-rc2 + the 4 patches on the wiki" on?
I have only tested on x86-64 and cross-compiled "x86-64-32".
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.
