[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <799c5a58c2501762e7e1e5c81c1e2cfd@smtp.hushmail.com>
Date: Fri, 09 Mar 2012 19:05:43 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: .include bug
I think I just stumbled over a bug with the .include directive. It's a
little odd I never noticed before.
Current john.conf ends like this:
# dumb-force UTF-32, in an external file
.include "$JOHN/dumb32.conf"
# Dynamic ($dynamic_n$) scripting code, in an external file
# also shows/tests that .include <file> works the same as .include
"$JOHN/file"
.include <dynamic.conf>
...but it turns out that last comment is not true: If I run john from
another directory than CWD (eg. ../run/john) I can use dumb32 but I
can't use -sub=list. If I run it from CWD (eg. ./john) it works fine.
It seems this is a problem is released Jumbo as well as latest git. I'm
not quite sure where to start looking.
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.
