Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fbbac11eceba7cd39aa4a772965a9908@smtp.hushmail.com>
Date: Thu, 28 Jun 2012 11:02:11 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Re: Re: Failed self test for raw-sha1-ng (linux-x86-sse2i
 OMP)

On 2012-06-28 10:52, Tavis Ormandy wrote:
> Pull request sent, FWIW, I had to ssh to another machine because it doesn't
> compile with gcc 3.4 which the machine I'm sitting at right now has, with
> this error:
> 
> gcc -c -Wall -O2 -fomit-frame-pointer -I/usr/local/include     -msse2
> -DHAVE_CRYPT -DHAVE_DL -DUSING_ICC_S_FILE -funroll-loops keepass2john.c
> keepass2john.c:1: error: stray '\239' in program
> keepass2john.c:1: error: stray '\187' in program
> keepass2john.c:1: error: stray '\191' in program
> 
> $ xxd keepass2john.c | head -1
> 0000000: efbb bf2f 2a20 6b65 6570 6173 7332 6a6f  .../* keepass2jo
> 
> Are those byteorder marks? Interesting that I can only remove them in vim
> with vim -b :-)
> 
> I'll send a pull request for that as well, and a compilation fix for my
> code.

Committed. The BOM problem was already fixed so now it's fixed twice
according to git history. That should keep it from coming back :)

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.