search

nagyistoce / grimwepa

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

autocrack-ng at 10K Ivs #10

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Select any attack mode
2. Begin attack

What is the expected output? What do you see instead?
ivs captured > 0 : ivs captured = 0

auto crack never starts I am guessing this is because the ivs are updating

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

v1.10 Alpha 2

Backtrack 4 usb live disk

Aircrack-ng v 1.1 r.1704

Please provide any additional information below.

IVS are getting update in main interface of program

Original issue reported on code.google.com by ondro...@gmail.com on 24 May 2010 at 7:40

GoogleCodeExporter commented 9 years ago 
I think I know what may be happening:

Grim Wepa waits for data packets from the access point that it can use to 
arp-replay,
chopchop, fragment, etc.
Grim Wepa does not look at the # of IVS while waiting for these packets; it has 
no
need to, since it hasn't exactly "started" the attack at that point.

So while Grim Wepa's status is "waiting for packets...", don't expect the 
'captured
IVS' to go up.  The "waiting for packets" is actually waiting for a packet of a
certain length, so that it can arp-replay the packet,  fragment the packet into 
a new
packet, use chop-chop on the packet, etc. After a valid packet is found and 
replayed,
then the packet-capture will begin.

If Grim Wepa still says 'captured ivs: 0' AFTER it has begun the attack 
(replaying
packets), then we do have an issue.

Let me know if this problem resolves itself.

Thanks!

Original comment by der...@gmail.com on 25 May 2010 at 12:15

GoogleCodeExporter commented 9 years ago 
I've experienced a similar issue. When collecting IVs, every now and then the 
IVs
will turn to 0 but the crack will still succeed after a while.

Original comment by ext...@gmail.com on 25 May 2010 at 3:30

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

Original comment by der...@gmail.com on 28 May 2010 at 1:51

GoogleCodeExporter commented 9 years ago 
this issue re-occurs in v1.10 alpa 5, the iv captures are not updates even 
though the
attack had already started.. so i had to manually watch airodump windows and hit
"start cracking" manually

Original comment by JinP...@gmail.com on 29 May 2010 at 6:47

GoogleCodeExporter commented 9 years ago 
have u tried running it without install it? i also have the same problem but 
after
run it direct without install it, the ivs display the capture iv.

Original comment by sabri...@gmail.com on 3 Jun 2010 at 7:55

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

Original comment by der...@gmail.com on 9 Jun 2010 at 8:51

GoogleCodeExporter commented 9 years ago 
This issue involves the current-working-directory -- after install, the CWD 
changes.

This issue has been fixed in v1.10 ALPHA 6.  This issue should not reappear in 
alpha 6 or later revisions.

I'm going to leave this issue open until I have confirmations that the issue is 
solved.  I would appreciate it if you could confirm that this is fixed.  

If you have grimwepa v1.10 alpha 4 or above, you could help test the 'check for 
updates' option in the installer window.  In theory, grimwepa will download and 
run the latest version (you would still need to install the newer version 
manually).

I wanted to say Thank You to everyone for reporting this issue.  It would have 
taken me months to find this bug!

Original comment by der...@gmail.com on 9 Jun 2010 at 9:30