Please login or register.

Login with username, password and session length
Pages: [1] 2 3 ... 10
 on: June 13, 2019, 09:22:45 pm 
Started by EssJay - Last post by EssJay
Sounds like I should delve into Crunch and JTR a bit  :D

 on: June 13, 2019, 09:02:52 pm 
Started by EssJay - Last post by misterx
There aren't really ways around it, it's just about building a great wordlist and there are tools to do the job. JTR and crunch are two of them but there are a lot around to build wordlist from different source, like cewl, rsmangler and people keep posting new tools on GitHub. Kali has a list of all the tools in there and some small example for each:

 on: June 13, 2019, 08:18:38 pm 
Started by EssJay - Last post by EssJay
I'm new to Kali.  I just figured out how to crack my own network with aircrack-ng wpa/wpa2.  I believe I understand the basics.  Such as if the word is not in the wordlist then it will not be cracked, but there are tools to work around that such as crunch or JTR.  I havent looked into crunch or JTR.  Do you have any recommendations as far as challenges for beginners is concerned?  I do have a 2 year degree, but that degree is just a broad over view of Linux basics, among many other things I learned.  Sorry if I put this in the wrong spot, I was looking for a general discussion area, but sometimes i'm an id10t.

 on: June 12, 2019, 01:38:16 pm 
Started by gdb328 - Last post by misterx
In your case, airodump-ng will hop on channels, which will make deauth probably useless.

 on: June 12, 2019, 11:59:10 am 
Started by gdb328 - Last post by satyam158
Hello gdb328,
I am in a similar scenario but not able to reproduce the steps you have mentioned. I have 4 terminal open out of those on three I am running the following command:
aireplay-ng --deauth 0 wlan0mon -c <client mac> -a <AP mac1>
aireplay-ng --deauth 0 wlan0mon -c <client mac> -a <AP mac2>
aireplay-ng --deauth 0 wlan0mon -c <client mac> -a <AP mac3>

On fourth terminal I am running airodump-ng  wlan0mon --essid <ssid name>

Can you please help me here?

 on: June 08, 2019, 05:39:41 am 
Started by Javiervs - Last post by Javiervs
Thanks misterx and dmkgrim80 for your replies. After a Lenovo update left my Kali partition inaccessible, I've decided to buy an Alfa Network AWUS036NHA and use VirtualBox from now on. For that reason I can't test anything else, but maybe a possible solution may be to kill the Bluetooth service, since it also depends on the wireless device. That's all speculation from my part.

If you want, close this topic or keep it open so more people can look for answers regarding the device, and eventually find a solution.

Thank you very much!

 on: June 08, 2019, 02:15:38 am 
Started by Mike - Last post by ehumiupaqifs
The carbimazole proptosis viagra buy in canada cheapest viagra canadian pharmacy amoxicillin 500mg capsules online female cialis vaccine, threadworm, listen, <a href="">viagra</a> <a href="">lowest price for generic viagra</a> <a href="">viagra in pharmacy</a> <a href="">amoxicillin 500mg capsules</a> <a href="">female cialis for sale</a> photocoagulated garden drained efecto viagra mujeres walmart viagra 100mg price cialis online pharmacy canadian pharmacy price amoxicillin buy cheapest female cialis cell paraphimosis, crashes maculopathy.

 on: June 08, 2019, 12:33:34 am 
Started by Javiervs - Last post by dmkgrim80
Qualcomm Atheros QCA9377 is troublesome. Dont know if the firmware is crashing or not. I have Qualcomm Atheros QCA9377 in a Acer Aspire E15.

my Qualcomm Atheros QCA9377 just isnt wireless network adapter its also a bluetooth chip 2 in 1 functions.

 on: June 06, 2019, 02:14:16 pm 
Started by Javiervs - Last post by misterx
There seems to be something wrong with the hardware as shown in the logs  you attached:

[   33.604258] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[   33.604274] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
[   33.604283] pcieport 0000:00:1c.0:   device [8086:9d12] error status/mask=00001000/00002000
[   33.604289] pcieport 0000:00:1c.0:    [12] Timeout       

I was referring to which points to the mailing lists. Mention the error above that keeps repeating (as well as an output of lspci).

 on: June 06, 2019, 07:41:09 am 
Started by Javiervs - Last post by Javiervs
I have done the dist-upgrade you suggested, but it's still not showing APs. I've also checked rfkill and it says there's nothing blocked. What I found in google about the errors from dmesg is that there might be some incompatibility with the hardware and Linux, or some kernel bug, I'm not sure. But the people posting those errors are having serious problems with their wifi connection and their logs are flooded with that error to the point they weigh many GB after a single week, while my wifi works perfectly fine, so I have no idea what it is about.

I have attached the dmesg log so you can take a look. If something else comes to your mind, let me know and I'll try it, or if you need any other info or logs, just ask me and I'll provide them.

Thank you.

Links about the AER corrected error:

Edit: I forgot about the Linux-wireless mailing list you suggested. I have googled it but I'm not sure what it is. Am I supposed to send an email to that address about the issue?

Pages: [1] 2 3 ... 10