Aircrack-ng forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Aircrack-ng 1.6 release

Pages: 1 ... 8 9 [10]
 91 
 on: December 23, 2020, 08:22:01 pm 
Started by 100jay - Last post by 100jay
Hi, i am having probs with running aircrack i am using kali version Linux version 5.9.0-kali4-amd64 (devel@kali.org) (gcc-10 (Debian 10.2.0-19) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 5.9.11-1kali1 (2020-12-01)

i have got the password file and the pcap file in the correct locations and i can navigate to them using the terminal so i guess the addresses are correct but when i run the command this happens

# aircrack-ng -w /home/large/Desktop/info/passwords/rockyou.txt ~/home/large/Desktop/okey.pcap
Reading packets, please wait...
Opening /root/home/large/Desktop/okey.pcap
Failed to open '/root/home/large/Desktop/okey.pcap' (2): No such file or directory
Read 0 packets.

No networks found, exiting.
 the pcap file was captured by fern and extracted by wireshark using the EAPOL filter

i am very new to kali and and aircrack so any help would be much appreciated

 92 
 on: December 23, 2020, 03:39:56 am 
Started by Fpa - Last post by Fpa

https://www.youtube.com/watch?v=3QPIZRLmXbY



https://docs.microsoft.com/en-us/cpp/c-language/cpp-integer-limits?view=msvc-160


Tools used to test in video

https://sourceforge.net/projects/hexcinary/

 93 
 on: December 20, 2020, 10:58:36 pm 
Started by alfa98 - Last post by misterx
It could be a bug. It should be resolved either in development or in 1.6.

What version do you have?

 94 
 on: December 19, 2020, 02:37:55 am 
Started by frankfooter32 - Last post by frankfooter32
Hello

Equipment: Alfa AWUS036ACH Wi-Fi adapter AC1200
Fresh Install of Kali Linux, fully updated (not on a VM)

I have been running across this same "bad beacon" error (sometimes with "DEAUTH" in front of it) when trying to run besside-ng.  I am running besside-ng after I run the sudo airmon-ng start wlan1command, which I get the message stating that I should run the airmon-ng check kill, which I do.  Resulting in:

Killing these processes:

    PID Name
    615 wpa_supplicant

Then Im running : sudo airodump-ng wlan1.  Which gives me plenty of network data for all access points, with BSSIDs, channels etc. I capture the BSSID and enter it in the "X's" below.

But when I run sudo besside-ng -b XX:XX:XX:XX:XX:XX wlan1.  It gives me the bad beacon errors below.  So I thought maybe I needed to turn back on my network manager (as before it had been being closed with the check kill command above, even though it wasnt in my example this time) and I still cant get besside-ng to handshake.

Anyone seen this before and can please help a noob out?

Thank you!


sudo besside-ng -b XX:XX:XX:XX:XX:XX wlan1
[18:18:07] Let's ride
[18:18:07] Autodetecting supported channels...
[18:18:07] Resuming from besside.log
[18:18:07] Appending to wpa.cap
[18:18:07] Appending to wep.cap
[18:18:07] Logging to besside.log
[18:18:08] | Scanning chan 02
Bad beacon
[18:18:09] / Scanning chan 05
Bad beacon
[18:18:09] - Scanning chan 06
Bad beacon
[18:18:09] \ Scanning chan 06
Bad beacon
[18:18:10] | Scanning chan 06
Bad beacon
[18:18:10] / Scanning chan 06
Bad beacon
[18:18:10] \ Scanning chan 06
Bad beacon
[18:18:10] | Scanning chan 06
Bad beacon
[18:18:10] / Scanning chan 06
Bad beacon
[18:18:10] - Scanning chan 06
Bad beacon
[18:18:10] | Scanning chan 06
Bad beacon
[18:18:10] / Scanning chan 06
Bad beacon
[18:18:10] - Scanning chan 06
Bad beacon
[18:18:10] - Scanning chan 06
Bad beacon
[18:18:10] | Scanning chan 06
Bad beacon
[18:18:10] / Scanning chan 06
Bad beacon
[18:18:10] - Scanning chan 06
Bad beacon
[18:18:10] \ Scanning chan 07
Bad beacon
[18:18:10] | Scanning chan 07
Bad beacon
[18:18:10] / Scanning chan 07
Bad beacon
[18:18:10] - Scanning chan 07
Bad beacon
[18:18:10] | Scanning chan 08
Bad beacon
[18:18:10] / Scanning chan 08
Bad beacon
[18:18:10] - Scanning chan 08
Bad beacon
[18:18:10] \ Scanning chan 08
Bad beacon
[18:18:11] - Scanning chan 10
Bad beacon
[18:18:11] / Scanning chan 11
Bad beacon
[18:18:11] - Scanning chan 11
Bad beacon
[18:18:11] | Scanning chan 11
Bad beacon
[18:18:11] / Scanning chan 11
Bad beacon
[18:18:11] - Scanning chan 11
Bad beacon




 95 
 on: December 16, 2020, 09:34:33 pm 
Started by alfa98 - Last post by alfa98
Hi.
Today I tried to see the networks in 5ghz with airodump-ng. Every time (and I have tried many adapters) I can never see ESSIDs with 5GHZ,
Code: [Select]
<length: 0> always comes out. Why??

Thanks

 96 
 on: December 13, 2020, 08:16:01 pm 
Started by Dark-Star88 - Last post by misterx
They're both broadcom.

 97 
 on: December 13, 2020, 07:02:30 am 
Started by Dark-Star88 - Last post by Dark-Star88
Avoid broadcom, and looking at your card, it only has 2 connectors, so a 3x3 card is out of question.

The ORIGINAL card does, but when I opened up the laptop, there were 3 wire connectors. 2 plugged in and one left unused.

So go for Dell Wireless 1830 (DW1830) or Foxconn U40H039.00?

 98 
 on: December 12, 2020, 03:01:54 am 
Started by Dark-Star88 - Last post by misterx
Avoid broadcom, and looking at your card, it only has 2 connectors, so a 3x3 card is out of question.

 99 
 on: December 11, 2020, 06:20:51 pm 
Started by MacGyver - Last post by Aditya Negi
Hi zDog,
- Your capture file is not clean (contains many handshake) and Aircrack-ng is confused by this.
- Before using "wpaclean":
Code: [Select]
jano:~/aircrack-ng/test$ wpaclean suhod-01_clean.cap suhod-01.cap
Pwning suhod-01.cap (1/1 100%)
Net 64:70:02:73:eb:c6 TP-LINK_SUHOD
Done

- And repeat the attack:
Code: [Select]
jano:~/aircrack-ng/test$ aircrack-ng -w password2.lst suhod-01_clean.cap
Opening suhod-01_clean.cap
Read 3 packets.

   #  BSSID              ESSID                     Encryption

   1  64:70:02:73:EB:C6  TP-LINK_SUHOD             WPA (1 handshake)

Choosing first network as target.

Opening suhod-01_clean.cap
Reading packets, please wait...

                                 Aircrack-ng 1.2 beta2 r2354

                   [00:00:00] 236 keys tested (328.38 k/s)

                           KEY FOUND! [ qwer1234 ]

      Master Key     : 82 F4 75 82 B2 D3 AB 2B 45 1F 62 4F C0 19 E7 B3
                       43 86 F5 AD D4 C5 7C 35 47 02 F1 27 0C 26 E7 01

- I attach the new capture file clean.

Bye Jano

The same thing happening to me.
I tried your method too but the result is the same "KEY NOT FOUND"
Please also check my .cap file I attached.

and password is "aditya12"

 100 
 on: December 11, 2020, 06:18:06 pm 
Started by MacGyver - Last post by Aditya Negi
Hi zDog,
- Your capture file is not clean (contains many handshake) and Aircrack-ng is confused by this.
- Before using "wpaclean":
Code: [Select]
jano:~/aircrack-ng/test$ wpaclean suhod-01_clean.cap suhod-01.cap
Pwning suhod-01.cap (1/1 100%)
Net 64:70:02:73:eb:c6 TP-LINK_SUHOD
Done

- And repeat the attack:
Code: [Select]
jano:~/aircrack-ng/test$ aircrack-ng -w password2.lst suhod-01_clean.cap
Opening suhod-01_clean.cap
Read 3 packets.

   #  BSSID              ESSID                     Encryption

   1  64:70:02:73:EB:C6  TP-LINK_SUHOD             WPA (1 handshake)

Choosing first network as target.

Opening suhod-01_clean.cap
Reading packets, please wait...

                                 Aircrack-ng 1.2 beta2 r2354

                   [00:00:00] 236 keys tested (328.38 k/s)

                           KEY FOUND! [ qwer1234 ]

      Master Key     : 82 F4 75 82 B2 D3 AB 2B 45 1F 62 4F C0 19 E7 B3
                       43 86 F5 AD D4 C5 7C 35 47 02 F1 27 0C 26 E7 01

- I attach the new capture file clean.

Bye Jano

The same thing happening to me.
I tried your method too but the result is the same "KEY NOT FOUND"
Please also check my .cap file I attached.

and password is "aditya12"

Pages: 1 ... 8 9 [10]