search

http403 / pyrit

Automatically exported from code.google.com/p/pyrit
0 stars 0 forks source link

remember what workunit we exit from. #40

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
jacob@Lappy:~$ pyrit -e SonyCenter batch
Pyrit 0.2.5-dev (svn r170) (C) 2008, 2009 Lukas Lueg
http://pyrit.googlecode.com
This code is distributed under the GNU General Public License v3

Working on ESSID 'SonyCenter'
^Cocessed 3/7444 workunits so far (0.0%); 1207 PMKs per second.
Interrupted...
jacob@Lappy:~$ pyrit -e SonyCenter batch
Pyrit 0.2.5-dev (svn r170) (C) 2008, 2009 Lukas Lueg
http://pyrit.googlecode.com
This code is distributed under the GNU General Public License v3

Working on ESSID 'SonyCenter'
^Cocessed 1/7444 workunits so far (0.0%); 1618 PMKs per second.
Interrupted...
jacob@Lappy:~$

What is the expected output? What do you see instead?
1/7441

What version of the product are you using? On what operating system?
R 170

Please provide any additional information below.
If we run all night, and want too use pc in the morning, and not yet finish

Original issue reported on code.google.com by cha...@gmail.com on 4 Sep 2009 at 9:24

GoogleCodeExporter commented 9 years ago 
Pyrit does not "remember" the workunits that are already computed but checks 
for that
in the moment it reads it's specific key. It does not re-compute workunits that 
have
already been computed before.

You'll see that on the second run Pyrit skips some units and finishes e.g. at 
75% (in
case you did 25% on the first run).

I'll take care that the numbering is more clear in 0.2.5

Original comment by lukas.l...@gmail.com on 4 Sep 2009 at 10:07