-
```
getting following when trying to capture handshake with wifite:
[+] scanning for wireless devices...
[+] enabling monitor mode on wlan0... done
[+] initializing scan (mon0), updates at 5 sec i…
-
```
getting following when trying to capture handshake with wifite:
[+] scanning for wireless devices...
[+] enabling monitor mode on wlan0... done
[+] initializing scan (mon0), updates at 5 sec i…
-
```
getting following when trying to capture handshake with wifite:
[+] scanning for wireless devices...
[+] enabling monitor mode on wlan0... done
[+] initializing scan (mon0), updates at 5 sec i…
-
```
getting following when trying to capture handshake with wifite:
[+] scanning for wireless devices...
[+] enabling monitor mode on wlan0... done
[+] initializing scan (mon0), updates at 5 sec i…
-
```
getting following when trying to capture handshake with wifite:
[+] scanning for wireless devices...
[+] enabling monitor mode on wlan0... done
[+] initializing scan (mon0), updates at 5 sec i…
-
## Background
Related to #102 , it's always felt awkward to have the same SQS queue for both regular operation and for retroactive analysis:
- New binaries added to the BinaryAlert bucket might …
-
Nothing critical. These errors are probably known but I'm adding it as an issue so you can track it:
```
11-19 15:10:49.523 E/ (732): sensors_sysfs_write: open failed! -1
11-19 15:10:49.523 E/…
-
i get this error message:
`root@kali:~# wifite
.;' `;,
.;' ,;' `;, `;, WiFite v2 (r87)
.;' ,;' ,;' `;, `;, `;,
:: :: : ( ) : :: …
-
I get this thousands of time each day on our pool:
2018-01-29 16:27:32 [pool] (Thread 19) Malformed message from 31.148.112.18: ��S1��Y�����e�~0眽/�X�[�6�~UZZ�+�/�,�0̨̩����/5
It happens consisten…
-
```
getting following when trying to capture handshake with wifite:
[+] scanning for wireless devices...
[+] enabling monitor mode on wlan0... done
[+] initializing scan (mon0), updates at 5 sec i…