You. Are. Doing. It. Wrong.
Read the man page, come back, and tell me why my previous statement was correct. Oddly enough, doing so will give you a spoon-feeding-hint on you how to solve your problem as well.
I'm trying to write a bash script to chk wpa2 from txt list 12 characters but it's seems that iwconfig dosent accept 12 characters when command 'iwconfig key ' is entred? any suggestion?
thx for helping
You. Are. Doing. It. Wrong.
Read the man page, come back, and tell me why my previous statement was correct. Oddly enough, doing so will give you a spoon-feeding-hint on you how to solve your problem as well.
Still not underestimating the power...
There is no such thing as bad information - There is truth in the data, so you sift it all, even the crap stuff.
That too! But I meant this
Still not underestimating the power...
There is no such thing as bad information - There is truth in the data, so you sift it all, even the crap stuff.
so with iwconfig Passphrase is currently not supported.
i tried with s:mykey didnt work as well
the wpa2 i'am using looks like that 70460E726089
any other way?
i guess i have to edit the wpa_supplicant.conf
#
ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
ap_scan=1
fast_reauth=1
network={
ssid=”SSID”
psk=”WPApassword”
priority=5
}
#
but how to use it to intregate it with bash script to do chk from list?
I don't get what you are trying to do ?? What are you checking ? Why are you checking it ? Maybe add some more detail to your post.
i'am trying write a bash script who will connecte to my AP and try different wpa2 keys from a txt list
as follow:
echo "adding static IP address configuration ..."
ifconfig $1 192.168.1.200 netmask 255.255.255.0 2>/dev/null
route del default gw 192.168.1.1 2>/dev/null
echo "adding default gateway ..."
route add default gw 192.168.1.1 2>/dev/null
echo -en "trying key: ";
for key in `cat $3`
do
echo -en "$key "
iwconfig $1 key $key
# if AP is pingable then we're in!
if ping -c 4 192.168.1.1 | grep "64 bytes from" > /dev/null
then
echo -en "\nvalid key found!: $key\n"
echo $key > $2.found.txt
echo "found key was saved on $2.found.txt"
route del default gw 192.168.1.1 2>/dev/null
break
fi
done
route del default gw 192.168.1.1 2>/dev/null
but 12 characters wpa2 iwconfing dosent support it
Correct, because iwconfig does either encryption on or off, it is only going to support one type of encryption (stands to reason really, if you couldn't find a way to configure whether it was WEP or WPA, then there probably isn't a way to do it).
Edit the wpa config file, kill wpa_supplicant, connect, ping, if necessary, loop again.
Prepare for a punishingly slow script, but it's not a bad idea - I was working on something identical with scapy a while ago.
Edit: On the topic of integration, use sed to modify the psk= line.
Still not underestimating the power...
There is no such thing as bad information - There is truth in the data, so you sift it all, even the crap stuff.
Still not underestimating the power...
There is no such thing as bad information - There is truth in the data, so you sift it all, even the crap stuff.