Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [day] [month] [year] [list]
Date: Mon, 25 Jun 2012 02:22:28 +0200
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: Use a different format name for raw-sha1-ng, because of max. pw len
 15 instead of 55

To let relbench compare an implementation which supports a maximum
password length of 15 with one that supports a maximum password length
of 55 would IMHO not be correct.
That's why, make sure raw-sha1-ng uses a different format name.

ALexander wanted all different implementations of one algorithm to use
different format names - at least for implementations with different
features (like different maximum password length supported) I agree,

With this patch, raw-sha1-ng uses "Raw SHA-1 (pwlen <= 15)" instead of
"Raw SHA-1".

Frank

>From 635840e9a09c64331f8a50277fe85de9a0edc83b Mon Sep 17 00:00:00 2001
From: Frank Dittrich <frank_dittrich@...mail.com>
Date: Mon, 25 Jun 2012 02:21:12 +0200
Subject: [PATCH] Use a different format name for raw-sha1-ng, due to max.
 pwlen 15

---
 src/rawSHA1_ng_fmt.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/src/rawSHA1_ng_fmt.c b/src/rawSHA1_ng_fmt.c
index 1115fe6..fd034db 100644
--- a/src/rawSHA1_ng_fmt.c
+++ b/src/rawSHA1_ng_fmt.c
@@ -605,7 +605,7 @@ static int sha1_fmt_cmp_exact(char *source, int cuont)
 struct fmt_main sha1_fmt_ng = {
     .params                 = {
         .label              = "raw-sha1-ng",
-        .format_name        = "Raw SHA-1",
+        .format_name        = "Raw SHA-1 (pwlen <= 15)",
         .algorithm_name     =
 	"128/128 "
 #if defined(__XOP__)
-- 
1.7.7.6


Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ