|
Message-Id: <A928706C-FF86-4569-B6DA-F78C8F1DA8E4@gmail.com> Date: Fri, 14 Aug 2015 09:32:01 +0800 From: Lei Zhang <zhanglei.april@...il.com> To: john-dev@...ts.openwall.com Subject: Re: Lei's weekly report #15 > On Aug 14, 2015, at 9:02 AM, jfoug@....net wrote: > > I copied (in the shell) from my main git repo to the temp clone I made of your sha2 branch, and the 'can not include' problem went away. The ".include [section]" code was not working if there was no colon (like .include [rules:sometype]). The Options section has not : in it. So when I changed the john-local.conf file in the test suite root dir, it requires the current updated jumbo code. I am not sure why your update into your github branch is not pulling that current file (if that is hte problem), but I built your code, and got the same problem. I copied through the shell from my main working repo, and things were fine. Thats all I can explain ;) Oh, I know what's going on. I did get the latest update, but forgot to rebuild the binary... A rebuilding just solves this error. BTW, I've merged that sha2 branch into bleeding-jumbo. Yet it's still not 100% OK. After running ./jtrts.pl episerver form=episerver_sha1 guesses: 1476 -show=1476 0:00:00:00 DONE : Expected count(s) (1500) [!!!FAILED1!!!] .pot CHK:episerver_sha1 guesses: 1476 0:00:00:00 DONE [PASSED] (1476 val-pwd) form=episerver_sha256 guesses: 1476 0:00:00:00 DONE [PASSED] .pot CHK:episerver_sha256 guesses: 1476 0:00:00:00 DONE [PASSED] (1476 val-pwd) form=episerver_sha1-utf8 guesses: 1403 -show=1403 0:00:00:00 DONE : Expected count(s) (1500) [!!!FAILED1!!!] .pot CHK:episerver_sha1-utf8 guesses: 1403 0:00:00:00 DONE [PASSED] (1403 val-pwd) form=episerver_sha256-utf8 guesses: 1437 -show=1437 0:00:00:00 DONE : Expected count(s) (1500)(1202) [!!!FAILED1!!!] .pot CHK:episerver_sha256-utf8 guesses: 1437 0:00:00:00 DONE [PASSED] (1437 val-pwd) Seems you'll need to tweak jtrts.dat a bit more :) Thanks, Lei
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.