If this is your first visit, be sure to
check out the Forum Rules by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Re: New FERN WIFI CRACKER

I was running fern.py directly... tried running execute.py and it seems to work correctly... maybe a short "README" to suggest how to run it?

Also it needs a function to shut down and clean up after itself. There is no good way to shut down WEP cracking after it is started without leaving aireplay-ng and airodump-ng running... so if you want to change attack modes or if you don't find the WEP key you have to manually clean up.

Also it creates new VAPs every time its started - not necessarily a bad thing but another thing to manually clean up.

A "stop" function that would kill all the stray processes would be very helpful, along with a button to manually create the VAPs would be good.

But I do think this is a very good start on a useful tool.

Originally Posted by savioboyz

When a program crashes, python always prints the exceptions raised.... (fern.py) is the main program ,(execute.py) runs fern.py but first of all cd's into its directory.... The rest are ui generated files...

Re: New FERN WIFI CRACKER

Originally Posted by cw5301

I was running fern.py directly... tried running execute.py and it seems to work correctly... maybe a short "README" to suggest how to run it?

Also it needs a function to shut down and clean up after itself. There is no good way to shut down WEP cracking after it is started without leaving aireplay-ng and airodump-ng running... so if you want to change attack modes or if you don't find the WEP key you have to manually clean up.

Also it creates new VAPs every time its started - not necessarily a bad thing but another thing to manually clean up.

A "stop" function that would kill all the stray processes would be very helpful, along with a button to manually create the VAPs would be good.

But I do think this is a very good start on a useful tool.

Hmm!, actually it does cleanup after certain attack events, on line 1246 you find this

It does not kill processes until attack wep key is found.. which is logical.. it the dump files were deleted during attack.. wep key would never be found..

You find "killall" command on numerous lines in the source code.

And the cleanup is also always done.. But when a new attack is initiated attack.. this is logical beacause there would be times where aircrack was not able to find key from your dictionary file, and you need to get the dump file so you can use it with an exetrnal cracker.. The dump file will be there until you press the new attack button