search

n0x00 / pyrit

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

will not finish Batch processing, hangs on final WU #269

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Pyrit 0.4.1 will not finish Batch processing, hangs on final WU
2. Pyrit needs to fix this, also needs to automatically resume processing of 
next essid
3.Question: What is the consquence of termination a node thats processing work 
units on the DB, does that db get marked for reprocessing, or does it remain 
"marked" as processed?

What is the expected output? What do you see instead?

Processed 2321/2321 workunits so far (100.0%); 2685 PMKs per second..

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

2.6.32-28-generic #55-Ubuntu SMP Mon Jan 10 21:21:01 UTC 2011 i686 GNU/Linux
This is NON GPU acceleration, regular pyrit build of Pyrit 0.4.1-dev (svn r297)

Please provide any additional information below.

Original issue reported on code.google.com by mrfantas...@aol.com on 26 Feb 2011 at 9:05

GoogleCodeExporter commented 9 years ago 
What I meant to say was

Question: What is the consquence of terminating a node thats processing work 
units on the DB, does that Work Unit  get marked for reprocessing, or does it 
remain "marked" as processed?

Original comment by mrfantas...@aol.com on 26 Feb 2011 at 9:08

GoogleCodeExporter commented 9 years ago 
Gentlemen, disregard this post, I found the problem, Pyrit does indeed continue 
on to the next essid as I thought it should.

I would like to know What is the consquence of terminating a node thats 
processing work units on the DB, does that Work Unit  get marked for 
reprocessing, or does it remain "marked" as processed?

Original comment by mrfantas...@aol.com on 27 Feb 2011 at 6:05

GoogleCodeExporter commented 9 years ago 
Issue 323 has been merged into this issue.

Original comment by lukas.l...@gmail.com on 31 May 2011 at 4:40

GoogleCodeExporter commented 9 years ago 
I can confirm that I am experiencing the same issue in 0.4.1-dev (svn r308). 
Using the 'attack_batch' option instead of 'batch' resulted in the remaining 
work units being completed.

Original comment by duncanmc...@gmail.com on 13 Aug 2012 at 6:11