Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 13 Aug 2015 20:02:13 -0500
From: "" <>
Subject: Re: Lei's weekly report #15

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 ;)

I added this method into the TS, because I had added items into the  
[Options] section and these were not being picked up in the TS, because I  
was simply re-writing the entire [Options] section. Now, I include the  
options section items into a 'new' Options section, and then update just  
the items I want to update. So if new items get added to options, they  
will simply be there within the TS.


On Thu, 13 Aug 2015 19:47:29 -0500, Lei Zhang <>  

>> On Aug 14, 2015, at 8:31 AM, wrote:
>> I have pulled your source.  Your src/config.c does not have the latest  
>> changes.
> That's strange... I just pulled from upstream, and the latest update to  
> config.c is:
> commit 1a287d362eed196b3fbc67147992bc4e6285b515
> Author: jfoug <>
> Date:   Mon Aug 10 20:42:55 2015 -0500
>     config:  Could not .include [section] which did not have a colon  
> char, such as [Options]
> Is something wrong?
> 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.