Please login or register.

Login with username, password and session length
Advanced search  


Aircrack-ng 1.6 release

Pages: 1 [2] 3 4 ... 10
 on: January 03, 2021, 10:31:28 pm 
Started by Hibbie - Last post by misterx
-a is rarely needed.
Skip setting the BSSID for now, and only specify the PCAP that contains the handshake,

We do have extensive documentation in the wiki, and that includes a WPA cracking tutorial. In case you need to look at the PCAP to see check the handshake, check out

 on: January 03, 2021, 01:01:27 pm 
Started by Mastiff - Last post by Mastiff
And solved! By one line...

Code: [Select]
sudo apt-get install -y raspberrypi-kernel-headers bc build-essential dkms git
I'll quietly dissappear now...  ;D

 on: January 02, 2021, 08:28:30 am 
Started by Hibbie - Last post by Hibbie
I'm going through the wifi cracking procedure as an assignment for school. I'm doing this on my own wifi, of which I know the password. I'm using this procedure:

I can:
  • Set the wifi adapter to monitoring, see all the traffic pass by
  • Take the MAC of my own router and monitor it specifically
  • See my phone connect to this wifi
  • Trigger the disconnect so it reconnects, the handshake is successfully capture

However, the below command, if I understand correctly, runs a list of possible passwords against handshakes found in the capture, to attempt to decrypt them. When doing this with a file that contains only the correct password, it returns 'no key found' however. It does states 1 possible candidates, and when I add more lines to the text file it shows more possible candidates.

I've checked the password over and over but it is in fact correct. Is there another reason this could be failing? Am I missing something? I'm using Kali live, the encryption is wpa2 but the command should be the same for wpa & wpa2, no?

aircrack-ng –a2 –b 00:14:BF:E0:E8:D5 –w /root/wpa.txt  /root/Desktop/*.cap

 on: January 02, 2021, 08:01:02 am 
Started by Mastiff - Last post by Mastiff
Thank you very much for answering! And I'm sorry if I'm imprecise.  :-[ I mean that the USB card is physically there, but the network interface isn't showing, so either the driver isn't working because of something I did, or there is something else that prevents it from working.

And no, in my naivity I thought installing a newer driver would uninstall the original driver automatically. I have worked with Windows and Windows servers for around 35 years, but I'm no Linux man. I only use Pi's for home automation, and I have not needed to do any manual driver upgrades before, so I'm totally out of my depth here. But here's the dmesg-output:

Code: [Select]
[ 3007.841266] v3d fec00000.v3d: MMU error from client L2T (0) at 0x3b41000, pte invalid
[ 3028.294082] usb 1-1.1.2: new high-speed USB device number 7 using xhci_hcd
[ 3028.424814] usb 1-1.1.2: New USB device found, idVendor=0b05, idProduct=1853, bcdDevice= 0.00
[ 3028.424831] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3028.424845] usb 1-1.1.2: Product: 802.11ac NIC
[ 3028.424859] usb 1-1.1.2: Manufacturer: Realtek
[ 3028.424872] usb 1-1.1.2: SerialNumber: 123456
[ 3028.545025] 8814au: disagrees about version of symbol module_layout

Edit: If you could tell me what I need to remove the previous driver, I could go back one image, remove that, do the full upgrade over LAN and then install the new drivers again.

Edit 2: I tried to do a sudo make uninstall with the first drivers, and it did something:

Code: [Select]
sudo make uninstall
rm -f /lib/modules/5.4.79-v7l+/kernel/drivers/net/wireless//88XXau.ko
/sbin/depmod -a 5.4.79-v7l+

But it gives the same result when plugging the USB wifi as above, with symbol layout. I googled a bit and found out that it could be rlated to kernel, so here's my output:

Code: [Select]
cat /proc/version
Linux version 5.4.79-v7l+ (dom@buildbot) (gcc version 8.4.0 (Ubuntu/Linaro 8.4.0-3ubuntu1)) #1373 SMP Mon Nov 23 13:27:40 GMT 2020

It said to check with gcc too, but that didn't give me anything:

Code: [Select]
gcc: fatal error: no input files
compilation terminated.

 on: January 01, 2021, 05:41:26 pm 
Started by Rampler - Last post by misterx
You might have to find a way to compile a newer version of aircrack-ng for this (if possible current git), as 1.5.2 is pretty old by now.

 on: January 01, 2021, 05:38:51 pm 
Started by ZUWN - Last post by misterx
Assuming the laptop you describe is the one that crashes, set-up kdump so you can capture the kernel crash.

You may also try doing the stuff from a tty which might show the kernel panic

 on: January 01, 2021, 05:34:32 pm 
Started by Mastiff - Last post by misterx
What do you mean by "the USB card just isn't loaded"?
Did you remove the old driver before installing the new one?
Is there any error in dmesg when you plug the card?

 on: December 29, 2020, 08:16:24 am 
Started by Mastiff - Last post by Mastiff
I hope this isn't considered off topic.  :-[ I have been using the rtl8812au driver for my Asus USB-AC68 since this summer, for a Pi that's in my fishing boat and connected to the cabin. I use the connection to turn off and on lights on the boat to check that it's OK during storms.  ;D But a month or so ago I did an upgrade of the Pi, and the driver stopped working. I went back to the backup I always do before any changes and left it at that. Then I saw that the latest drivers are different for 8812 and 8814, so I tried to do an update, with these commands:

Code: [Select]
git clone
cd rtl8814au
sudo make install

I changed the makefile to allow Pi and not i386 to get it working, and it seemed like it worked. But no way. On a new upgrade of the Pi and a reboot, and the USB card just isn't loaded. And I have no idea what to look for. Maybe it's still using the old driver, since I didn't know how to uninstall that? I know the card's still there with lsusb, so it's a driver problem. Can somebody please help me out here?

 on: December 25, 2020, 09:35:29 pm 
Started by Fpa - Last post by Fpa
I tried using my dehex tool from ( dehex -r 0FFF0000 | aircrack-ng test-01.cap -e test -w - )

Im using aircrack-ng windows when my dehex gets to APPROX. FFFFFFFF, in aircrack-ng it freezes.

I did some poking around, I cant seem to find how or where the overflow occurs....

tried poking in,
- next_key()
- next_dict()
- crack_wpa_thread()
- wpa_receive_passphrase()

youre better at c code than i probably am, so can someone please let me know if you find where the overflow is?

I dont get it, aircrack just freezes up!

 on: December 25, 2020, 03:34:31 pm 
Started by ZUWN - Last post by ZUWN
When I'm finishing hacking and sending packets either to send the wi-fi down, or to discover the router's pass (this with aireplay) in the end my laptop crashes, I don't know why.

Equipment features:
Processor: Intel® Core ™ i7-10510U Quad-Core, 1.80 GHz with Turbo up to 4.90 GHz, 8 MB Cache
RAM memory:
8GB (1x8GB) DDR4 2666MHz
2 x SO-DIMM slots (1 x free / 1 x occupied) for full expandability up to 64GB
Display: 15.6 "Full HD (1920x1080), IPS Level, 60Hz, 45% NTSC, Thin Bezel
Graphics Card: Intel® UHD Graphics
Storage: 512GB NVMe PCIe Gen3x4 SSD
Webcam: HD Type (30fps @ 720p)
Communications: Intel Wireless-AC 9560 (2x2 a / c) + Bluetooth 5.0
SO: Parrot SO (Linux)

Pages: 1 [2] 3 4 ... 10