[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <5DC6DB5C-9B92-4065-9AC6-748BAF0C035C@picturestogether.com>
Date: Sun, 2 Jun 2013 08:51:22 -0700
From: Martin <martin@...turestogether.com>
To: john-dev@...ts.openwall.com
Subject: Log errors and threads not terminating after successful crack
After a successful crack of my own password as a test, I looked at the john.log file out of curiosity and noticed the following (see below).
First, that the other threads continued running for a 1/2 hour after the 8th thread had cracked the password.
Second, that the only reason the other threads appear to have stopped is that there was an error processing some of the rules.
This was a single-crack run. The rules below are the ones that bombed:
# Try the second half of split passwords
-s x**
-s-c x**MlQ
I did not create these rules, they were already present in the john.conf file.
My questions:
I just noticed that the john.conf file was missing the '[Incremental:ASCII]' section (I was copying and pasting together my own conf file and missed that section). I'm assuming that's why I got the errors. Can someone confirm?
Shouldn't the successful Cracked status by one of the threads in Single Crack mode signal the other threads that they can terminate?
--- from john.log
8 0:01:00:52 + Cracked ?
8 0:01:00:52 Session completed
1 0:01:00:40 - Rule #38: '-c <*>2!?Ac$7' accepted as '<*>2!?Ac$7'
1 0:01:02:25 - Rule #39: '-c <*>2!?Ac$4' accepted as '<*>2!?Ac$4'
...
7 0:01:26:41 - Rule #53: '<*>2!?AlI' accepted
7 0:01:28:33 - Rule #54: '-c <*>2!?AcP' accepted as '<*>2!?AcP'
4 0:01:30:04 - Rule #55: '-c <*>2!?AcI' accepted as '<*>2!?AcI'
4 0:01:31:54 - Rule #56: '-s x**' rejected
4 0:01:31:54 - Rule #57: '-s-c x**MlQ' rejected
4 0:01:31:54 Proceeding with "incremental" mode: ASCII
4 0:01:31:54 ! Unknown incremental mode: ASCII
4 0:01:31:54 Terminating on error
5 0:01:30:07 - Rule #55: '-c <*>2!?AcI' accepted as '<*>2!?AcI'
5 0:01:31:57 - Rule #56: '-s x**' rejected
5 0:01:31:57 - Rule #57: '-s-c x**MlQ' rejected
5 0:01:31:57 Proceeding with "incremental" mode: ASCII
5 0:01:31:57 ! Unknown incremental mode: ASCII
5 0:01:31:57 Terminating on error
7 0:01:30:19 - Rule #55: '-c <*>2!?AcI' accepted as '<*>2!?AcI'
7 0:01:32:05 - Rule #56: '-s x**' rejected
7 0:01:32:05 - Rule #57: '-s-c x**MlQ' rejected
7 0:01:32:05 Proceeding with "incremental" mode: ASCII
7 0:01:32:05 ! Unknown incremental mode: ASCII
7 0:01:32:05 Terminating on error
1 0:01:30:19 - Rule #55: '-c <*>2!?AcI' accepted as '<*>2!?AcI'
1 0:01:32:06 - Rule #56: '-s x**' rejected
1 0:01:32:06 - Rule #57: '-s-c x**MlQ' rejected
1 0:01:32:06 Proceeding with "incremental" mode: ASCII
1 0:01:32:06 ! Unknown incremental mode: ASCII
1 0:01:32:06 Terminating on error
3 0:01:30:26 - Rule #55: '-c <*>2!?AcI' accepted as '<*>2!?AcI'
3 0:01:32:09 - Rule #56: '-s x**' rejected
3 0:01:32:09 - Rule #57: '-s-c x**MlQ' rejected
3 0:01:32:09 Proceeding with "incremental" mode: ASCII
3 0:01:32:09 ! Unknown incremental mode: ASCII
3 0:01:32:09 Terminating on error
2 0:01:30:27 - Rule #55: '-c <*>2!?AcI' accepted as '<*>2!?AcI'
2 0:01:32:10 - Rule #56: '-s x**' rejected
2 0:01:32:10 - Rule #57: '-s-c x**MlQ' rejected
2 0:01:32:10 Proceeding with "incremental" mode: ASCII
2 0:01:32:10 ! Unknown incremental mode: ASCII
2 0:01:32:10 Terminating on error
6 0:01:30:38 - Rule #55: '-c <*>2!?AcI' accepted as '<*>2!?AcI'
6 0:01:32:14 - Rule #56: '-s x**' rejected
6 0:01:32:14 - Rule #57: '-s-c x**MlQ' rejected
6 0:01:32:14 Proceeding with "incremental" mode: ASCII
6 0:01:32:14 ! Unknown incremental mode: ASCII
6 0:01:32:14 Terminating on error
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.
