You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I removed reaver 1.4 and installed reaver 1.6 and the script gives me this error:
+---------------------------------------------------------------------------------+
| [+] If the BSSID in green this mean that device is vulnerable. |
| [+] If the BSSID in yellow this mean that device is may be vulnerable or aren't.|
| [+] If the BSSID in red this mean the wps of that device is Locked. |
| [+] If the BSSID in Purple this mean that device is has a default pin or aren't.|
+---------------------------------------------------------------------------------+
ID BSSID CH PWR WPS Locked Ver ESSID
cat: /tmp/HT-WPS-Breaker055924/wash.txt: No such file or directory
cat: /tmp/HT-WPS-Breaker055924/wash.txt: No such file or directory
cat: /tmp/HT-WPS-Breaker055924/wash.txt: No such file or directory
cat: /tmp/HT-WPS-Breaker055924/wash.txt: No such file or directory
cat: /tmp/HT-WPS-Breaker055924/wash.txt: No such file or directory
cat: /tmp/HT-WPS-Breaker055924/wash.txt: No such file or directory
cat: /tmp/HT-WPS-Breaker055924/wash.txt: No such file or directory
cat: /tmp/HT-WPS-Breaker055924/wash.txt: No such file or directory
The text was updated successfully, but these errors were encountered:
I removed reaver 1.4 and installed reaver 1.6 and the script gives me this error:
+---------------------------------------------------------------------------------+
| [+] If the BSSID in green this mean that device is vulnerable. |
| [+] If the BSSID in yellow this mean that device is may be vulnerable or aren't.|
| [+] If the BSSID in red this mean the wps of that device is Locked. |
| [+] If the BSSID in Purple this mean that device is has a default pin or aren't.|
+---------------------------------------------------------------------------------+
ID BSSID CH PWR WPS Locked Ver ESSID
The text was updated successfully, but these errors were encountered: