Should you buy something? Pretend you already have two USB WiFi cards (or one USB and one internal) that are monitor and frame injection capable. Even if this isn't possible with off-the-shelf Atheros radios, then what is the second best option?
Then add two wireless USB cards (at least one of which with 5GHz cover). At the moment I tend to use an alfa card with external antenna for the 2.4GHz coverage and a D-Link DWA-160 for the 5GHz piece. The USB passthrough from VMWare workstation has been reliable in my experience, although it's sometimes a little random as to whether VMWare will grab a USB device as you connect it to the physical port or whether you need to manually connection it through VM--> Removable devices.
As an aside for the host system piece I'm looking at using a Thinkpad Twist to make use of a tablet form-factor which would run the VMWare setup ok. At the moment the touch drivers seem a bit flaky but I imagine that'll clear up.
To cover android as it gets a mention in comments, at the moment it is possible to get monitor mode but only with very specific hardware and the software is a bit limited. Details on the Android PCAP page. Outside of that there are a number of reasonable stumbler clients for android now, which are useful for tracking down APs that are broadcasting and also for gathering wireless data without toting a laptop around.
Backtrack-Linux.org has an official page on Installing BT4 in VMware. However, this article doesn't specify VMware Player, VMware Workstation, VMware Fusion, VMware ESX, or VMware ESXi (let alone the version numbers). It should work in any of them, but here is a specific guide on VMware Workstation (probably 7.1 -- the latest). There's a nice little YouTube video in the comments section regarding VMware Player, which is nice -- but not extra informative in any particular direction (nor did any of the linked videos, as catchily named as possible, really relate back to the original issue, which is support of WiFi and aircrack-ng).
The main problem is that any WiFi card that works well with aircrack-ng (like the Alfa AWUS036H highly suggested card, which is external USB with the SMA antenna connector) must be USB in order to be accessible from a guest BT4 OS. There are a few comments in this link which discuss this absolute fact.
When using VMware (or any hypervisor), you must use a USB wireless adapter. If you are trying to use the host's built-in wireless device, you cannot use it in VMware (or any hypervisor) since the built-in wireless devices will be shown as virtual Ethernet adapters.
While I don't see a reason to run VMware or Virtual-PC instead of VirtualBox (although I'll certainly try both), what does remain is that in order to complete certain attacks, such as MITM or frame injection along with monitoring maximum performance -- you will need 2 WiFi USB adapters, but it's been that way for Mac OS X and other platforms for about 4 years now.
Researching about cracking WIFI passwords, I found the aircrack-ng suite of applications, and, after some time of study, I managed to complete the mission of finding the wifi password of my house xD
There is an application that currently does this, it's called crunch, it's basically a word generator. And can send this parameter to aircrack using the following command from the console:
In the real world, it has no applicability, because, with the junction of the C# application with aircrack-ng, the number of attempts per second has been greatly reduced, it is around 8 thousand attempts per second. This I my computer with a core i9, and 32Gb of memory.
First Step: Download and uncompress the Aircrack-ng file. Personally, I prefer to move the .rar file to the desktop to have a more clear working area. If your web browser does not ask you where to save the file, then just go to your "Downloads" section of your file explorer.
Third Step: Go to your 'Local Disk (C:) and open the folder "Program Files" or "Program Files (x86)" depending on your windows architecture. Since my Windows is 64-bit I will choose the 'Program Files' folder.
In this new window, you have to write (path) inside the "Variable name:" box. Then, you will have to paste the address that you copied before in step #4 inside the "Variable value:" box. All the procedures are shown below.
Step 3: Aireplay-ng window will show up. Set amount of deauth packets to send (default: 10) and wait for station to appear (you can choose if several are found or type in a station mac address manually (format: xx-xx, xx:xx, xxxx)). Hit 'Run deauth (aireplay-ng)'. If you see 'Success' on top of the window, then a handshake was received successfully. If not, try changing the station or amount of packets.
Step 4: Now, you can close aireplay-ng window. In the main window, press 'Open aircrack-ng', select .cap file (capture file located wherever you set it to in Step 1). Select a wordlist, hit 'Start aircrack-ng / hashcat' and hope for the best ;)
Sounds like you ran out of memory. Since you're booting a live disc off USB, and your system looks to have a small amount of ram, depending on the ISO you used(they have instructions to make a mini-iso as well), you're most likely doing something that has eaten up all the ram since these boot into memory using a ramdisk. Alternatively, you could try installing it locally and dual booting into kali, which will have better results, but you're system alone for windows 7, should be slow as shit with those specs to begin with. 4GB RAM would be recommended for Windows 7 alone.
While Kali doesn't need more than about a gig(if natively installed), this would need more if using in a live disc, since that 1GB of ram is used for the expansion of the OS itself + whatever else you are doing, scanning, logging, etc.
You must keep your USB boot device inserted for the duration otherwise this is the sort of thing that would happen. If you did that it means that either the USB socket is kinda flaky or the storage is itself corrupt. So try a different USB port and if that didn't change anything re-write the image to the USB device. Also, verify the checksum for your download (which you should've done anyways) to make sure the corruption didn't occur there.
Aircrack-ng is a network software suite consisting of a detector, packet sniffer, WEP and WPA/WPA2-PSK cracker and analysis tool for 802.11 wireless LANs. It works with any wireless network interface controller whose driver supports raw monitoring mode and can sniff 802.11a, 802.11b and 802.11g traffic. Packages are released for Linux and Windows.[2]
Aircrack-ng is a fork of the original Aircrack project. It can be found as a preinstalled tool in many security-focused Linux distributions such as Kali Linux or Parrot Security OS,[3] which share common attributes as they are developed under the same project (Debian).[4]
Aircrack was originally developed by French security researcher Christophe Devine,[5] its main goal was to recover 802.11 wireless networks WEP keys using an implementation of the Fluhrer, Mantin and Shamir (FMS) attack alongside the ones shared by a hacker named KoreK.[6][7][8]
Wired Equivalent Privacy was the first security algorithm to be released, with the intention of providing data confidentiality comparable to that of a traditional wired network.[10] It was introduced in 1997 as part of the IEEE 802.11 technical standard and based on the RC4 cipher and the CRC-32 checksum algorithm for integrity.[11]
Due to U.S. restrictions on the export of cryptographic algorithms, WEP was effectively limited to 64-bit encryption.[12] Of this, 40 bits were allocated to the key and 24 bits to the initialization vector (IV), to form the RC4 key. After the restrictions were lifted, versions of WEP with a stronger encryption were released with 128 bits: 104 bits for the key size and 24 bits for the initialization vector, known as WEP2.[13][14]
The initialization vector works as a seed, which is prepended to the key. Via the key-scheduling algorithm (KSA), the seed is used to initialize the RC4 cipher's state. The output of RC4's pseudo random generation algorithm (PRGA) follows a XOR operation in combination with the plaintext, and produces the ciphertext.[15]
The IV is constrained to 24 bits, which means that its maximum values are 16,777,216 (224), regardless of the key size.[16] Since the IV values will eventually be reused and collide (given enough packets and time), WEP is vulnerable to statistical attacks.[17] William Arbaugh notes that a 50% chance of a collision exists after 4823 packets.[18]
In 2004, the Wi-Fi Alliance announced that WEP had been superseded by Wi-Fi Protected Access (WPA). In 2004, with the ratification of the full 802.11i standard (i.e. WPA2), the IEEE declared that both WEP and WEP2 have been deprecated.[19]
Wi-Fi Protected Access (WPA) was designed to be implemented through firmware updates rather than requiring dedicated hardware.[20] While still using RC4 at its core, it introduced significant improvements over its predecessor. WPA included two modes: WPA-PSK (WPA Personal) and WPA Enterprise.
WPA-PSK (Wi-Fi Protected Access Pre-Shared Key), also known as WPA Personal, used a variant of the Temporal Key Integrity Protocol (TKIP) encryption protocol. It improved security by implementing the following features:
In WPA-PSK, each packet was individually encrypted using the IV information, the MAC address, and the pre-shared key as inputs. The RC4 cipher was used to encrypt the packet content with the derived encryption key.[22]
Additionally, WPA introduced WPA Enterprise, which provided enhanced security for enterprise-level networks. WPA Enterprise employed a more robust authentication mechanism known as Extensible Authentication Protocol (EAP). This mode required the use of an Authentication Server (AS) such as RADIUS (Remote Authentication Dial-In User Service) to validate user credentials and grant access to the network.
In 2015, the Wi-Fi Alliance recommended in a technical note that network administrators should discourage the use of WPA and that vendors should remove support for it and rely instead on the newer WPA2 standard.[24]
795a8134c1