Please login or register.

Login with username, password and session length
Pages: 1 [2] 3 4 ... 10
 on: June 05, 2019, 10:12:15 pm 
Started by Javiervs - Last post by misterx
airmon-ng kills/stops network managers. In Kali, it's just service network-manager start to restart it. By the way, killing network manager then putting in monitor mode is the correct way to do it.

Two things you can try:
- Do a dist-upgrade, it will upgrade the kernel, then reboot and try again.
- Check that rfkill doesn't report the device as blocked.

Have you googled that error message from dmesg?

Other than that, I'm pretty much out of ideas of what is wrong, I would have done the exact same steps as you did. Maybe something's wrong with the firmware or the hardware itself. You could bring it up to Linux-wireless mailing list.

 on: June 05, 2019, 09:45:56 am 
Started by Javiervs - Last post by Javiervs
I'm a newbie at using Aircrack, Linux, and hacking in general and I'm having trouble capturing traffic with airodump-ng.

I'm using kali, installed on a partition on the main drive in dual boot with Windows 10. My laptop is a Lenovo Yoga 720 with an integrated wireless device Qualcomm Atheros QCA9377, which, to my knowledge, should theoretically support mointor mode.

I have followed these steps:

- Searched on google for similar problems.
- Used apt-get update and apt-get upgrade.
- Used airmon-ng check kill and then airmon-ng start wlan0, then airodump-ng wlan0mon
- No AP appear, despite being many WiFi in range.
- No error messages appear up until this point and every step seems to work fine except for not showing any APs.
- Executing dmesg shows up many "AER: Corrected error received". Apart from that, I can only see a message saying "device wlan0mon entered promiscuous mode" when entering airodump-ng wlan0mon, but I'm not sure what I'm looking for.
- Using airmon-ng check kill permanently disables my WiFi connection until restart, while entering airmon-ng start wlan0 without entering before airmon-ng check kill disables my connection only until I enter airmon-ng stop wlan0mon. I'm not sure if this is normal behavior, but at this point both actions result in no APs showing up.

I'd appreciate any help regarding how to solve the issue or how to proceed in order to troubleshoot it.

Thanks in advance.

 on: May 30, 2019, 02:00:31 pm 
Started by peterfarge - Last post by peterfarge
Thanks for the answer :)
I try the src from github.

 on: May 30, 2019, 01:20:21 pm 
Started by peterfarge - Last post by misterx
Current version is 1.5.2. We have repositories that contain packages with the latest version:

However, I think there was a bug about it and it was fixed in the development version. If you really need it now, you can compile from the repo. Or you can wait for the release.

 on: May 30, 2019, 11:49:57 am 
Started by peterfarge - Last post by peterfarge
Hello Forum,

I have to save and resume a aircrack session if the wordlists is to long. I know the john the ripper examples and how they work. Now I have seen that since july 2018 there is a native way to save+resume with aircrack-ng. How does it work?

I think save+resume should work like this:
Code: [Select]
// Create Session (file savefile.session) and abort it when ever you want:
aircrack-ng -b 11:22:33:44:55:66 -w passwords.txt -N savefile.session handshake.pcap

// After aborting, resume the session:
aircrack-ng -R savefile.session

The first command results in an error message and no savefile.session is created:
"aircrack-ng --help" for help.

Quitting aircrack-ng...

I'm using Kali and I have done a apt-get update + upgrade.
Aircrack says its the 'Aircrack-ng 1.3' version.



 on: May 29, 2019, 03:40:48 pm 
Started by echo.plasmus - Last post by misterx
You have 100% chances of success when the correct password is in the list. And thus 0% when it isn't :)

 on: May 29, 2019, 12:02:02 am 
Started by echo.plasmus - Last post by jweb
My apologies to MisterX : The referenced author while not stating it in the text obviously changed his wordlist generation to : crunch 8 8 123ab -t a@@@@@b -o wordlist
This would have caused 15624 unique values to be generated which is exactly what the aircrack-ng result screen shows as the total number of keys to be tested. So.... I am now convinced that the WPA password must exist in the wordlist or aircrack-ng will never be successful.

 on: May 28, 2019, 06:01:55 pm 
Started by echo.plasmus - Last post by misterx
First, WPA passphrases are between 8 and 63 characters long. Anything shorter or longer will be ignored. That's explained in the FAQ if you want more details.

My guess is that he used crunch with the charset or 123ab with a passphrase length of 8 (min & max 8): crunch 8 8 123ab | aircrack-ng wpa.cap -w -
The use of STDIN is also documented.

 on: May 28, 2019, 03:24:22 pm 
Started by echo.plasmus - Last post by jweb
I'm a newbie myself and am curious about the same issue. I have been using a book entitled "Learn Ethical Hacking From Scratch" by Zaid Sabih. As an example of wordlists cracking he generated a wordlist containing words of 5 characters in length containing only 123ab. Using that wordlist he cracked a key of a1b1a11b. This would imply some additional folding taking place as the key, 8 characters in length, could not be present in a wordlist containing only words 5 characters in lenght. Please explain.

 on: May 28, 2019, 01:24:28 pm 
Started by echo.plasmus - Last post by misterx
No, it doesn't, each line is taken as is.

There are a few tools to do combination and they output the result on the screen, which can then be used with aircrack-ng: john [your parameters] | aircrack-ng wpa.pcap -w -

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