Hey, I released at last airgeddon v7.0 with WEP support performing an "All-in-One" attack against WEP networks. Very handy! ;) I'll keep developing and informing!
Hey, I released at last airgeddon v7.0 with WEP support performing an "All-in-One" attack against WEP networks. Very handy! ;) I'll keep developing and informing!
Where is the best place to download this????Quote:
Originally Posted by v1s1t0r
and thanks for all the hard work you do!
You can download it from here: https://github.com/v1s1t0r1sh3r3/airgeddon
Follow the instructions to download and install it. They are on wiki at Installation & Usage section: https://github.com/v1s1t0r1sh3r3/air...on%20&%20Usage
At the bottom, there are a special metion for Kali Linux users because there is a very easy to install .deb package. You will see the last version now is 7.02.
Regards.
Hi, I tried to run Airgeddon with the latest Nethunter on a nexus 10 but it thinks my network card is a non wifi card, tried a bunch of them. so is this script compatible with Nethunter or is there an easy fix for it?
No, sorry, I don't think so... because airgeddon needs xterm to open windows for attacks. so you need a X Window system running to connect. If you want to run it on Android, you can do it using "Linux Deploy" app installing for example a Kali Linux image. There you have a X window system and you can connect to it by VNC. Maybe a problem with this other configuration could be how to connect hardware to that linux (I didn't tested it). Not sure if using a OTG cable with an external USB wireless device could be an option.
Ok, Thanks. I will try it some day but i have a feeling that the network card will still show up *** non wifiQuote:
Originally Posted by v1s1t0r
its the same in linuxdeploy :(
always glad to see a nice answer instead of harassing me for not reading and looking everywhere before asking,Quote:
Originally Posted by v1s1t0r
Version 7.1 released. See the changelog here:
https://github.com/v1s1t0r1sh3r3/air...r/CHANGELOG.md
Oh my god! I re-read again the entire thread... and sorry undersc0re... you were right!! my mistake. I read your post about hashcat very quickly first time and I thought it was the "normal" error regarding the opencl drivers... but I didn't saw this:
Sorry for that. You are right, hashcat has been updated and now instead of hccap format a new one hccapx is needed. And you MiAl were right too...Quote:
Old hccap format detected! You need to update...
First time I saw hashcat 3.0 I fixed the opencl drivers and I updated the line command and the output parsing based on a hashcat version detection (old style for hashcat 2.x and new for 3.0)... but it seems in newer versions this mandatory format change for capture file was introduced.
Now I have a hashcat 3.5 fully working and I can do the needed tests... but the problem is I don't know exactly were this mandatory changed was introduced. I know it wasn't at 3.0 but not sure if maybe was at 3.20 or maybe at 3.30. Does anybody know exactly when was introduced? I need to know that exactly in order to detect version and then do the change or not to make airgeddon compatible with all versions... can anybody help with this? thank you.
Looks like they added support for it in version 3.30 from what I can tell. https://github.com/hashcat/hashcat/b...anges.txt#L111Quote:
Originally Posted by v1s1t0r