I have no idea how that happened unless you were running an old version of airodump-ng and even then, what the attacker can do is very limited, so it most likely happened outside (unless you have code/packets that can help reproduce the issue). Also, a...
↧