[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20040224140730.GA4356@openwall.com>
Date: Tue, 24 Feb 2004 17:07:30 +0300
From: Solar Designer <solar@...nwall.com>
To: announce@...ts.openwall.com
Subject: John the Ripper 1.6.37
Hi,
There's a new development version of John the Ripper. It may be
obtained at the usual location:
http://www.openwall.com/john/
The changes between John 1.6.36 and 1.6.37 include:
Support for OpenBSD/x86 with ELF binaries has been added. Previously,
only older versions of OpenBSD which still used a.out binaries were
fully supported. Thanks to demon for sending in the Makefile patch.
Support for Linux/x86-64 (both 32-bit with MMX and native 64-bit) has
been added. With native 64-bit builds for AMD x86-64, an older
version of Matthew Kwan's DES S-box expressions with standard gates
only is used because x86-64 is lacking AND-NOT and OR-NOT bitwise
operations. "make generic" will now also benchmark the two versions
of the S-box expressions and pick one which results in better
performance for the host system. Thanks to John Edward Scott for
making me do it and for testing.
An optimal version of the x86 assembly code is now chosen on Centaur
Technology processors (IDT Winchip to VIA C3 and beyond).
When generating a new charset file, John will now perform a self-test
of the specified compile-time CHARSET_* parameters to ensure they
don't cause a 64-bit integer overflow.
Several bugfixes have been applied, including to a recently introduced
bug with the --stdin option and to reporting of the c/s rate with
benchmarks on fast 32-bit systems with a large CLK_TCK (e.g. Win32).
Several compilation and compiler warning fixes have been applied,
which should have no effect on run-time behavior of John.
--
Alexander Peslyak <solar@...nwall.com>
GPG key ID: B35D3598 fp: 6429 0D7E F130 C13E C929 6447 73C3 A290 B35D 3598
http://www.openwall.com - bringing security into open computing environments
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.
