Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 17 Dec 2011 01:00:21 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: OpenMP for MD5-crypt

On 12/17/2011 12:37 AM, Solar Designer wrote:
> magnum -
>
> I am making the below change in -jumbo-5 such that the multiple threads
> are used in single crack mode as well.
>
> --- john-1.7.9-jumbo-4/src/MD5_fmt.c	2011-12-16 02:25:34 +0400
> +++ john-1.7.9-jumbo-5/src/MD5_fmt.c	2011-12-17 03:34:12 +0400
> @@ -79,9 +79,11 @@
>   {
>   	MD5_std_init(pFmt);
>   #if defined(_OPENMP)&&  defined(MD5_SSE_PARA)
> -	omp_para = OMP_SCALE * omp_get_max_threads();
> +	omp_para = omp_get_max_threads();
>   	if (omp_para<  1)
>   		omp_para = 1;
> +	fmt_MD5.params.min_keys_per_crypt = MD5_N * omp_para;
> +	omp_para *= OMP_SCALE;
>   	fmt_MD5.params.max_keys_per_crypt = MD5_N * omp_para;
>   #elif MD5_std_mt
>   	fmt_MD5.params.min_keys_per_crypt = MD5_std_min_kpc;
>
> Non-SIMD version of the code already used a similar approach.

Great! I didn't know there was a problem. How does this affect single 
mode? Would min=max work too or is that also bad?

magnum


Powered by blists - more mailing lists

Your e-mail address:

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