john-users - Re: MinGW build

Openwall Project		/home Owl JtR Pro crypt pam_passwdqc tcb phpass scanlogd popa3d msulogin / Linux BIND / advisories presentations / services donations / wordlists passwords / news community lists wiki CVSweb mirrors signatures
bringing security into open environments

Password Recovery Resources on the Net

[<prev] [next>] [<thread-prev] [thread-next>] [month] [year] [list]

Date: Tue, 02 May 2006 20:04:14 +0200
From: Michal Luczaj <regenrecht@...pl>
To:  john-users@...ts.openwall.com
Subject: Re: MinGW build

Solar Designer wrote:
>> "The return value [of times()] is the calling process' CPU time (_the
>> same value you get from clock()_. times returns (clock_t)(-1) to
>> indicate failure."
> Yes, the glibc documentation appears to be wrong in this respect.

On the same page of manual:

"The times function returns information about a process' consumption of
processor time in a struct tms object, _in addition_ to the process' CPU
time."

As stated above: processor time is stored in a struct while process' CPU
time is a return value of function. Does it make sense now?

>> What is more, after running --test, it seemed that everything was fine:
>> Benchmarking: Traditional DES [64/64 BS MMX]... DONE
>> Many salts:     593832 c/s real, 596535 c/s virtual
>> Only one salt:  538966 c/s real, 548912 c/s virtual
> Yes, this does look realistic.  Can you please try running two instances
> simultaneously to see how the numbers will change?

Here we go...

Many salts:     280809 c/s real, 284930 c/s virtual
Only one salt:  261091 c/s real, 266839 c/s virtual

Many salts:     293709 c/s real, 301609 c/s virtual
Only one salt:  256117 c/s real, 264183 c/s virtual

michal