Current PMKs/s is an inaccurate measurement

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Running pyrit attack_db with 'SOME' PMKs already generated

What is the expected output? What do you see instead?
An appropriate average of the current PMKs/s being processed.
Instead when pyrit runs through its own database with very high PMK/s this
throws off the current PMKs/s when it starts to generate the PMKs/s not in
the database.

What version of the product are you using? On what operating system?
r190 on Ubuntu 9.10 beta

Please provide any additional information below.
Perhaps only use the last 1 minute of data to calculate the average? I
think in a few other parts of the program this may be an issue. For example
when using batch process and I lower my CPU frequency because my laptop is
overheating, the PMKs/s takes a long time to drop to the correct speed. I
know I'm being pedantic but still whenever you have the time it would be
nice =P

Original issue reported on code.google.com by adam.k...@gmail.com on 24 Oct 2009 at 4:43

[GoogleCodeExporter]

Hi there, I use "time pyrit batch" to know from command line how much long pyrit
works, than it is easy to calculate Num_of_passwords/seconds. 

Why don't implement 2 "gettime()" at the start and at stop of execution of 
pyrit and
then do the easy calculation?

Original comment by pyrit.lo...@gmail.com on 16 Dec 2009 at 9:54

[GoogleCodeExporter]

fixed in r194.

Original comment by lukas.l...@gmail.com on 22 Dec 2009 at 6:03

[GoogleCodeExporter]

I said 'fixed'!

Original comment by lukas.l...@gmail.com on 1 Jan 2010 at 2:59

[GoogleCodeExporter]

Javascript-of-death-from-different-domain ?!

Original comment by lukas.l...@gmail.com on 1 Jan 2010 at 3:00

• Changed state: Fixed