Jump to content

Wifite & G.L.O.D


markcoker
 Share

Recommended Posts

hey so im using wifite (http://wifite.googlecode.com/svn/trunk/wifite.py) and the dip switches to create a autocrack of wireless.

its just basicly wifite.py -all -i mon0 -dict passwordlist.txt -aircrack

now this starts and works 25 - 50% of the time.

the other times it drops me from ssh. everything seems to crash and i can no longer access via wlan or eth.

lights are green only... i call it G.L.O.D (Green Light Of Death)

im finding it hard to pinpoint the issue as its not always happening. anyone else getting this error, i think its only when using the -all option (which is required if we want to automate wifite).

any help/ideas is appreciated. thanks :)

Edited by markcoker
Link to comment
Share on other sites

Problem 2: Serial doesnt drop to shell (my attempt to troubleshoot the above issue without network connectivity but for these current tests i can use pineapple like normal eg. wifi/ssh/web interface etc).

So im connecting using CP2102 to connect via minicom in ubuntu linux and on another pc windows 8.1 & putty.

3.3v // Not Connected (in what case is this used for the pineapple?)

G == GND

R == Rx

T == Tx

5v // Not connected

(order is as if im looking at serial end)

ive tried reversing Rx and Tx and power cycling many times no luck. I have prevously used the CP2102 to read serial data on a old router (havent tested tx yet).

Linux ubuntu 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 12.10
Release: 12.10
Codename: quantal

Welcome to minicom 2.6.1

OPTIONS: I18n
Compiled on May 1 2012, 13:36:18.
Port /dev/ttyUSB0

115200 8N1

ive gotten seemly random data (see below):

< s~~@~<                                         
@@<d2~?8tpA -
p8|@ "                            
 @~

:7:>?66?6ߟ

Any ideas?

Anyone experienced this issue?

Edited by markcoker
Link to comment
Share on other sites

Update:
Problem 2 fixed! Layer 1 issue haha, so replaced cable from pin to pin and it didnt work so i reversed pins

GND == G

RX == T

TX == R

Then i realised i was doing it wrong haha

of course Tx > Rx & Rx > Tx

For people that dont understand

you need to recieve the transmition from the pineapple USB RX < PINEAPPLE TX

the pineapple needs to recieve from pc USB TX > PINEAPPLE RX
and of course you need GND (ground)

How quickly you forget these things when you dont use it offen.

Hope this helps other people. Issue One still remains though, will update soon.

Edited by markcoker
Link to comment
Share on other sites

Starting Wifite                                                                 
                                                                                
[  550.190000] device mon0 entered promiscuous mode                             
[  561.740000] br-lan: port 2(wlan0) entered disabled state                     
[  561.740000] device eth0 left promiscuous mode                                
[  561.750000] br-lan: port 1(eth0) entered disabled state                      
[  561.770000] device wlan0 left promiscuous mode                               
[  561.770000] br-lan: port 2(wlan0) entered disabled state                     
Terminated                                                                      
root@Pineapple:/sd/wifi# [  564.680000] Removing MTD device #3 (rootfs_data) wi1
[  564.710000] System halted.


Finally we have a starting point!

anyone know whats happening?

from my understanding all of these statements are bad:

mon0 - promiscuous from monitor mode :(

br-lan port 2 - wlan0 disabled - (great! AP down :( )

eth0 le ft promiscuous mode mode - basicly pre-disabled state?

eth0 - now its disabled

wlan0 left promiscuous mode, again pre-disabled state (but was prevously disabled???)

br-lan port 2 (wlan0) - disabled again

Removing MTD device - (guessing sebkinne will know?)SD card?? sounds bad whatever it is, prob causes the system halt! (problem with firmware?/SD card maybe?)

system halted - we all know this is bad!

Edited by markcoker
Link to comment
Share on other sites

After looking into it further, this doesnt seem to be any help.

a halt command does the same

root@Pineapple:/# halt
root@Pineapple:/# [  228.840000] br-lan: port 2(wlan0) entered disabled state
[  228.840000] device eth0 left promiscuous mode
[  228.850000] br-lan: port 1(eth0) entered disabled state
[  228.860000] device wlan0 left promiscuous mode
[  228.860000] br-lan: port 2(wlan0) entered disabled state
[  229.240000] umount: sending ioctl 4c01 to a partition!
[  229.240000] umount: sending ioctl 4c01 to a partition!
[  231.270000] Removing MTD device #3 (rootfs_data) with use count 1
[  231.300000] System halted.

So Wifite (http://wifite.googlecode.com/svn/trunk/wifite.py) appears to force the system to halt.

Edited by markcoker
Link to comment
Share on other sites

This is what happened to me! Except I can't even get a shell through serial. I've been running wifite but not through the dip switches and without a dictionary attack.(I think I may have shutdown the pineapple without completely closing wifite.) I was hoping if I let it sit unplugged for a day or two and try the serial cable again I'll at least get a shell...

Edited by zz2Fac3zz
Link to comment
Share on other sites

This is what happened to me! Except I can't even get a shell through serial. I've been running wifite but not through the dip switches and without a dictionary attack.(I think I may have shutdown the pineapple without completely closing wifite.) I was hoping if I let it sit unplugged for a day or two and try the serial cable again I'll at least get a shell...

Are you able to get a shell normally? if you expect to get something when its just sitting with the green light on, you might be waiting for a while. i belive the system is halted, a power cycle should work and rerun wifite again.

where you running wifite.py with the -all switch?

Link to comment
Share on other sites

I've worked with wifite tonight and it works but I did experience a reboot. I am not using the all function... just ./wifite.py -aircrack

I cracked a WEP Access Point that had clients in about 7 mins. Which for the Pineapple is pretty good. Not getting a GLOD.

Link to comment
Share on other sites

Could you try with the -all tag? im almost certain now, that it is at the root of the cause. (the problem is i need that tag for it to automaticly start cracking) and i would like to avoid a total rewrite of wifite.

and thanks for your information :)

Edited by markcoker
Link to comment
Share on other sites

  • 3 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...