-
```
Hey so i did a wash check and it agve me an access point and i started the
reaver cracking...im at 35% now and i just realized that the access point is
WEP not wpa...i even verified this with ai…
-
```
Hey so i did a wash check and it agve me an access point and i started the
reaver cracking...im at 35% now and i just realized that the access point is
WEP not wpa...i even verified this with ai…
-
```
Hey so i did a wash check and it agve me an access point and i started the
reaver cracking...im at 35% now and i just realized that the access point is
WEP not wpa...i even verified this with ai…
-
```
Hey so i did a wash check and it agve me an access point and i started the
reaver cracking...im at 35% now and i just realized that the access point is
WEP not wpa...i even verified this with ai…
-
Ch. 30.5.2.4
-
This could be a btlejack issue rather than a Mirage issue, but when I run
```
sudo btlejack -c any -d /dev/ttyACM0 -d /dev/ttyACM1 -d /dev/ttyACM2
```
I can successfully see a known JustWorks pai…
jsmif updated
5 months ago
-
```
Hey so i did a wash check and it agve me an access point and i started the
reaver cracking...im at 35% now and i just realized that the access point is
WEP not wpa...i even verified this with ai…
-
```
Hey so i did a wash check and it agve me an access point and i started the
reaver cracking...im at 35% now and i just realized that the access point is
WEP not wpa...i even verified this with ai…
-
```
Hey so i did a wash check and it agve me an access point and i started the
reaver cracking...im at 35% now and i just realized that the access point is
WEP not wpa...i even verified this with ai…
-
```
Hey so i did a wash check and it agve me an access point and i started the
reaver cracking...im at 35% now and i just realized that the access point is
WEP not wpa...i even verified this with ai…