Aleksey Cherepanov | 1 May 23:55 2012
Picon

Aleksey's status report #2

My first week of work on the automated equipped working place of a hash
cracker was not very intensive. I will compensate it during next week due to
holidays.

I quoted my previous status report.

Done

> - New good project name
> 
> I have a timeline in my proposal. I think I will use it as a roadmap trying to
> move faster. So I think it would be nice to have it on the wiki but it needs
> good page name and thus good project name.

I put my choice onto 'Joan the Helper' name. It is not perfect. So comments
are welcome.

I started page for it: http://openwall.info/wiki/john/joan

There are my proposal and timeline. Markup still needs to be cleaned.

To do

- Fix markup on the wiki page

It is more about my misunderstood of DokuWiki markup language. So I need to
learn it a bit.

> - Keep and raise discussions
> 
(Continue reading)

Frank Dittrich | 2 May 11:21 2012
Picon

Re: Aleksey's status report #2

Hi Aleksey,

On 05/01/2012 11:55 PM, Aleksey Cherepanov wrote:
> My first week of work on the automated equipped working place of a hash
> cracker was not very intensive. I will compensate it during next week due to
> holidays.

nevertheless, thanks for the update.

> I quoted my previous status report.
> 
> 
> Done
> 
>> - New good project name
>>
>> I have a timeline in my proposal. I think I will use it as a roadmap trying to
>> move faster. So I think it would be nice to have it on the wiki but it needs
>> good page name and thus good project name.
> 
> I put my choice onto 'Joan the Helper' name. It is not perfect. So comments
> are welcome.

I agree that a good name is important, but I'm afraid I am not of much
help here. So let's see what others suggest.

> I started page for it: http://openwall.info/wiki/john/joan
> 
> There are my proposal and timeline. Markup still needs to be cleaned.

(Continue reading)

Lukas Odzioba | 2 May 16:48 2012
Picon

Re: Aleksey's status report #2

2012/5/1 Aleksey Cherepanov <aleksey.4erepanov@...>:
> I put my choice onto 'Joan the Helper' name. It is not perfect. So comments
> are welcome.

BJtR - brutal,
MJtR - mutli,
DJtR - distributed
JtR (s)team machine - team or steam :)
JcM John crack machine
JcT John cracking toolkit

Lukas

Brad Tilley | 2 May 21:37 2012

Re: Aleksey's status report #2

> 2012/5/1 Aleksey Cherepanov <aleksey.4erepanov@...>:
>> I put my choice onto 'Joan the Helper' name. It is not perfect. So
>> comments
>> are welcome.
>
> BJtR - brutal,
> MJtR - mutli,
> DJtR - distributed
> JtR (s)team machine - team or steam :)
> JcM John crack machine
> JcT John cracking toolkit
>
> Lukas

What about a play on words as a joke. We could be the third and final
generation of the joke:

Multics - time-sharing operating system.
Unix - multi-user operating system. Name meant to poke fun at 'Multics'
Johnix - multi-user password cracking system. Name meant to honour 'Unix'

Off-topic, and I'm only kidding.

Brad

Frank Dittrich | 6 May 19:44 2012
Picon

--show=LEFT output

Hi all,

we had a similar issue mentioned by magnum in the past, see
Message-ID: <4D824B35.5020908@...>
http://openwall.com/lists/john-users/2011/03/17/1
http://thread.gmane.org/gmane.comp.security.openwall.john.user/3347/focus=3524

$ cat passwd
user1:XXxzOu6maQKqQ:1001:1001:user 1:/home/user1:/bin/bash
user2:XXxzOu6maQKqQ:1002:1002:user 2:/home/user2:/bin/bash

$ ./john --show=LEFT passwd
user1:XXxzOu6maQKqQ

The --shown=LEFT output gets rid of information which might still be
helpful for cracking the remaining hashes.

Instead of just suppressing lines containing hashes which have been
cracked, --show=LEFT output removes all columns except user name and
hash, and it also prints each uncracked hash just once, even if it
appears multiple times in the input file.

This is unfortunate, because the information which is missing in john's
--show=LEFT output could still be useful for further cracking sessions,
especially for single mode.

Can we just change the behavior of --show=LEFT, possibly breaking some
scripts which rely on the current poutput? Or do we need to support the
current behavior in the future, so that a new --show=??? option is required?

(Continue reading)

Frank Dittrich | 6 May 21:59 2012
Picon

file name expansion for --wordlist= and file name starting with ~

Hi all,

did anybody else of you notice that for --wordlist=filename, even bash
auto-completion for file names starting with ~/ or ~user works, but john
fails to recognize e.g. --wordlist=~/test.txt?

With this command line
$ ./john --wordlist=~/test
afer pressing [tab], bash completes the command line to
$ ./john --wordlist=~/test.txt

But when I try to execute
$ ./john --wordlist=test.txt passwd
I get
fopen: ~fd/test.txt: No such file or directory

The above applies to all --opt=filename options, but I doubt I'll ever
use ~/ for any option except --wordlist.

Frank

Stephen John Smoogen | 6 May 22:52 2012
Picon

Re: file name expansion for --wordlist= and file name starting with ~

On 6 May 2012 13:59, Frank Dittrich <frank_dittrich@...> wrote:
> Hi all,
>
> did anybody else of you notice that for --wordlist=filename, even bash
> auto-completion for file names starting with ~/ or ~user works, but john
> fails to recognize e.g. --wordlist=~/test.txt?

Works for me, which says that the problem is either with your shell or
depends on the version of john you have. Neither of which you say.

$ john --session=DD --wordlist=~/x --pot=xyz.pot --format=raw-md5 y000
Loaded 10 password hashes with no different salts (Raw MD5 [SSE2i 10x4x3])
guesses: 0/80  time: 0:00:00:00 DONE (2012-05-06 14:51)  c/s: 285
trying: redhat - rhel
$ rpm -q bash john
bash-4.1.2-8.el6.x86_64
john-1.7.9-1jumbo5.el6.x86_64

So something in your shell is not expanding the items when it hands it
off to the program.

> With this command line
> $ ./john --wordlist=~/test
> afer pressing [tab], bash completes the command line to
> $ ./john --wordlist=~/test.txt
>
> But when I try to execute
> $ ./john --wordlist=test.txt passwd
> I get
> fopen: ~fd/test.txt: No such file or directory
(Continue reading)

Frank Dittrich | 7 May 01:07 2012
Picon

add support for LUKS encryption to wish list?

Since http://openwall.info/wiki/john/wishlist contains truecrypt and
FileVault, but doesn't mention LUKS (see
http://en.wikipedia.org/wiki/Linux_Unified_Key_Setup), should this be
added as well?

BTW: FileVault users might need to know this:
http://nakedsecurity.sophos.com/2012/05/06/apple-update-to-os-x-lion-exposes-encryption-passwords/

Frank

Dhiru Kholia | 7 May 08:01 2012
Picon

Re: add support for LUKS encryption to wish list?

On Mon, May 7, 2012 at 4:37 AM, Frank Dittrich
<frank_dittrich@...>wrote:

> Since http://openwall.info/wiki/john/wishlist contains truecrypt and
> FileVault, but doesn't mention LUKS (see
> http://en.wikipedia.org/wiki/Linux_Unified_Key_Setup), should this be
> added as well?
>

LUKS was on my TODO list at some point. Currently, bug fixing and
improvements to existing code are taking my time.

--

-- 
Cheers,
Dhiru
Aleksey Cherepanov | 7 May 10:02 2012
Picon

Re: file name expansion for --wordlist= and file name starting with ~

On Sun, May 06, 2012 at 02:52:47PM -0600, Stephen John Smoogen wrote:
> On 6 May 2012 13:59, Frank Dittrich <frank_dittrich@...> wrote:
> > did anybody else of you notice that for --wordlist=filename, even bash
> > auto-completion for file names starting with ~/ or ~user works, but john
> > fails to recognize e.g. --wordlist=~/test.txt?

It does not work for me too.

$ bash --version
GNU bash, version 4.2.20(1)-release (x86_64-pc-linux-gnu)
...
$ apt-cache show john
Package: john
Version: 1.7.8-1
...
Filename: pool/main/j/john/john_1.7.8-1_amd64.deb
...

> Works for me, which says that the problem is either with your shell or
> depends on the version of john you have. Neither of which you say.
> 
> $ john --session=DD --wordlist=~/x --pot=xyz.pot --format=raw-md5 y000
> Loaded 10 password hashes with no different salts (Raw MD5 [SSE2i 10x4x3])
> guesses: 0/80  time: 0:00:00:00 DONE (2012-05-06 14:51)  c/s: 285
> trying: redhat - rhel
> $ rpm -q bash john
> bash-4.1.2-8.el6.x86_64
> john-1.7.9-1jumbo5.el6.x86_64
> 
> So something in your shell is not expanding the items when it hands it
(Continue reading)


Gmane