New FERN WIFI CRACKER

[hellohello]

although I have not posted so much on the forums I have been watching and learning a lot.

although I know all the commands to do job this program is a time saver, what could take 5 minutes doing commands and stuff this program can do in less then a minuet sometimes.

looking at a screen on a computer on the road is dangerous, and this program lowers that danger by over 80%

I think this program will do well and will become very popular in a short amount of time, so I hope the community will work hard at perfecting its functionality and implement this program into backtrack, this will save much time in trying to figure things out.

best regards to the programmers of this program and many thanks for all the hard work.

I also would highly recommend that this program be a sticky on this this forum for easy finding, i feel its worth for everyone to try.

again, great work!

[Alaska_Nebreska]

First of all, thank you for trying. It's very pretty. But it just doesn't work.

When first executed, Fern changes my screen res from 1024x768 to 800x600 and then back to 1024x768. Why?

After Fern is loaded, I perform the initial scan, I'd like to tell what text is displayed beside the button, but I'm not getting up to walk over and read it...it's sooooooooooo small. Once the initial scan is complete this is the info displayed:

Unhandled exception in thread started by <bound method mainwindow.scan_wep of <__main__.mainwind ow object at 0xb743592c>>
Traceback (most recent call last):
File "fern.py", line 723, in scan_wep
detail_process1 = process[iterate]
IndexError: list index out of range

When I exit Fern, in the term box, I see this:

aircrack-ng: no process killed
airmon-ng: no process killed

Even if Fern loaded up and functioned properly, everything is far too small to read.

At this point, for me, I don't like it.

I am brutally honest, so take nothing personal from what I've said.
I really do think it's pretty to look at.

I'm running BT4-R2 fully up to date, and Fern 1.2

Thanks

[savioboyz]

First of all, thank you for trying. It's very pretty. But it just doesn't work.

When first executed, Fern changes my screen res from 1024x768 to 800x600 and then back to 1024x768. Why?

After Fern is loaded, I perform the initial scan, I'd like to tell what text is displayed beside the button, but I'm not getting up to walk over and read it...it's sooooooooooo small. Once the initial scan is complete this is the info displayed:

Unhandled exception in thread started by <bound method mainwindow.scan_wep of <__main__.mainwind ow object at 0xb743592c>>
Traceback (most recent call last):
File "fern.py", line 723, in scan_wep
detail_process1 = process[iterate]
IndexError: list index out of range

When I exit Fern, in the term box, I see this:

aircrack-ng: no process killed
airmon-ng: no process killed

Even if Fern loaded up and functioned properly, everything is far too small to read.

At this point, for me, I don't like it.

I am brutally honest, so take nothing personal from what I've said.
I really do think it's pretty to look at.

I'm running BT4-R2 fully up to date, and Fern 1.2

Thanks

ALrigt Alaska_Nebreska i understand your complains, while building fern i did not use any of the Qt Layouts because they did not allow me position the buttons and labels the way i wanted them. but although this ccomes with a disadvantage.. it will depend on a particular resolution to fit the program button and label properly. if you run the application at that 1024x768 with out first of all running at a suitable resolution, the texts will overlap or some text will become big and long to an extent that some get hidden, thats why the program does the adjustments , i explained this resolution adjustment in the google code page of which it is hosted...

detail_process1 = process[iterate]
IndexError: list index out of range

That exception is a bug i can get fixed:


for the "aircrack-ng: no pprocess killed ":

A user once reported that after closing up fern, the processes it called were still running.

therefore when you closed the application, that print out means that while you closed the appplication , aircrack and airmon-ng were not found running in the memeory
it would have also showed airodump-ng no process killed, but it did not print that airodump-ng no process killed ,beacuse it actually found the process in memory and killed it to free memory

run the aplication this way to initialize with the 1024x768 res:

python /usr/local/bin/Fern-Wifi-Cracker/fern.py

Then please report back.

Thanks Alaska_Nebreska

[savioboyz]

although I have not posted so much on the forums I have been watching and learning a lot.

although I know all the commands to do job this program is a time saver, what could take 5 minutes doing commands and stuff this program can do in less then a minuet sometimes.

looking at a screen on a computer on the road is dangerous, and this program lowers that danger by over 80%

I think this program will do well and will become very popular in a short amount of time, so I hope the community will work hard at perfecting its functionality and implement this program into backtrack, this will save much time in trying to figure things out.

best regards to the programmers of this program and many thanks for all the hard work.

I also would highly recommend that this program be a sticky on this this forum for easy finding, i feel its worth for everyone to try.

again, great work!

Thank you very much HelloHello .. Highly esteemed..

[savioboyz]

Unhandled exception in thread started by <bound method mainwindow.scan_wep of <__main__.mainwind ow object at 0xb743592c>>
Traceback (most recent call last):
File "fern.py", line 723, in scan_wep
detail_process1 = process[iterate]
IndexError: list index out of range



aircrack-ng: no process killed
airmon-ng: no process killed


Thanks

Unhandled exception in thread started by <bound method mainwindow.scan_wep of <__main__.mainwind                            ow object at 0xb743592c>>
Traceback (most recent call last):
  File "fern.py", line 723, in scan_wep
    detail_process1 = process[iterate]
IndexError: list index out of range

That Bug has been fixed

Update to revision 52

aircrack-ng: no process killed
airmon-ng: no process killed

Although there's nothing wrong with this output: nevertheless the function has been replaced with another similar alternative
That is from : "os.system()" to "commands.getstatusoutput()"

To verify the fact that , that ouput does not signify and exception:
try this on terminal :

"killall ping" Notice the output, it will return "ping: no process killed", because ping was not running on your memory

then fireup ping like this to keep the process busy "ping 127.0.0.1"

run "killall ping" again in another instance of terminal and notice the output

[pieface]

Just got around to trying this out. It worked as should and will deffo save me a few key strokes when needed.

Keep up the good work.

[snowman58]

Hi,

Sorry if this has been asked, but I couldn't find the answer.

Can this be added to the BT3/BT4 Live CD so it can be run similar to other pen testing tools?

Thanks for answering dumb questions!

[sickness]

Hi,

Sorry if this has been asked, but I couldn't find the answer.

Can this be added to the BT3/BT4 Live CD so it can be run similar to other pen testing tools?

Thanks for answering dumb questions!

There is a tutorial on the Wiki on how to customize your iso.

[dreammed]

let i check

[longjidin]

so many GUI for crack the wireless password.......!but i still like using the Old School (CMD) love the aircrack-ng..happy hunting!