Date: Mon, 14 Mar 2011 21:22:27 +0100 From: magnum <rawsmooth@...dband.net> To: john-dev@...ts.openwall.com Subject: Re: NT_fmt bug On 2011-03-12 02:38, magnum wrote: > If the SECOND character of a plaintext (buffered after set_key()) is > U+2000 or higher, it fails. ... > I am certain this has nothing to do with my UTF8 conversion but we never > get beyond U+00FF with pristine john so this never happened until now. This is now confirmed, it's in nt_crypt_all_x86_64(). If you download my UTF-8 patch (version 4 or later) from the wiki and un-comment the 8-bit self tests in lines 54 *and* 244-245 in NT_fmt.c you can test this for yourselves: make linux-x86-64 --> you will have the bug, failing self-test with --utf8 make generic --> it will work fine (BTW, shouldn't I be able to "make linux-x86-any" (or sse or mmx) on a 64-bit host, for testing? Do I just miss something in my binutils?) 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.