Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Mon, 11 Jan 2016 14:35:54 +0100
From: patpro@...pro.net
To: "john-users@...ts.openwall.com" <john-users@...ts.openwall.com>
Subject: format-all-details -> Max. password length in bytes

Hello,

Another noobish question I'm afraid. Unfortunately, when it comes to JtR I seem unable to find any proper answer with search engines…

I'm running John (jumbo) against some Salted-SHA1, and reading the log file, I've seen:

> Will reject candidates longer than 39 bytes

I was a bit surprised, so I've checked details for this hash format:

> ./john --list=format-all-details --format=Salted-SHA1
> Format label                         Salted-SHA1
>  Disabled in configuration file      no
> Min. password length in bytes        0
> Max. password length in bytes        39
> ../..


I wonder how those limits are set: how are they implemented, are they tunable at run time, and why 39 (arbitrary decision?) ?
However, I do remember that incremental is limited to 8 char. at compile time. But I'm interested in the limit set for formats.

> $ ./john --list=format-all-details | grep "Max. password length"
> Max. password length in bytes        8
> Max. password length in bytes        64
> Max. password length in bytes        15
> Max. password length in bytes        72
> Max. password length in bytes        125
> Max. password length in bytes        7
> ../..



thanks,
pat

Powered by blists - more mailing lists

Your e-mail address:

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.