some background informations about wlanhcx2psk:
wlanhcx2psk is a dynamic tool (so look for latest hcxtools updates on git). It doesn't calculate a matching candidate
(if you need matching candidates use routerkeygenPC). Instead it creates a range of candidates
- given by the ESSID and
- analyses of real candidates from http://wpa-sec.stanev.org/?nets
Depending on the
- number of networks found in the hccapx file,
- the length of an ESSID and
- the selected options
output can be something between 20000 and real big (> 50000000 candidates)!
You can help by submitting your capfiles to http://wpa-sec.stanev.org/?nets
in the following ways:
- submit your uncleaned raw cap to http://wpa-sec.stanev.org/?submit
- or pre-clean and submit the cap using:
$ wlancap2hcx -p precleaned.cap *.cap
(data frames, IPv4 or IPv6 frames extended EAPOL frames and some management frames are stripped out)
- or complete clean the cap:
$ wlancap2hcx -o test.hccapx *.cap
$ wlanhcx2cap -i test.hccapx -o wpasec
(single cap files containing only 1 handshake each mac_sta(!), please do not use -O option)
$ wlancap2wpasec wpasec*.cap
You can also convert your uncracked hccapx files back to cap and submit this cap:
$ wlanhcx2cap -i youruncracked.hccapx -o myuncracked
(single cap files containing only 1 handshake each mac_sta(!), please do not use -O option)
$ wlancap2wpasec myuncracked*.cap
As "bonus" you can download a list of found candidates (updated whenever a new candidate was found) direct from here:
http://wpa-sec.stanev.org/dict/cracked.txt.gz
The pre-clean option (wlancap2hcx -p) is also 100% compatible to cap2hccapx.
But keep in mind: a (pre-)cleaned cap is useless for analysis purpose!!!!
wlanhcx2psk is a dynamic tool (so look for latest hcxtools updates on git). It doesn't calculate a matching candidate
(if you need matching candidates use routerkeygenPC). Instead it creates a range of candidates
- given by the ESSID and
- analyses of real candidates from http://wpa-sec.stanev.org/?nets
Depending on the
- number of networks found in the hccapx file,
- the length of an ESSID and
- the selected options
output can be something between 20000 and real big (> 50000000 candidates)!
You can help by submitting your capfiles to http://wpa-sec.stanev.org/?nets
in the following ways:
- submit your uncleaned raw cap to http://wpa-sec.stanev.org/?submit
- or pre-clean and submit the cap using:
$ wlancap2hcx -p precleaned.cap *.cap
(data frames, IPv4 or IPv6 frames extended EAPOL frames and some management frames are stripped out)
- or complete clean the cap:
$ wlancap2hcx -o test.hccapx *.cap
$ wlanhcx2cap -i test.hccapx -o wpasec
(single cap files containing only 1 handshake each mac_sta(!), please do not use -O option)
$ wlancap2wpasec wpasec*.cap
You can also convert your uncracked hccapx files back to cap and submit this cap:
$ wlanhcx2cap -i youruncracked.hccapx -o myuncracked
(single cap files containing only 1 handshake each mac_sta(!), please do not use -O option)
$ wlancap2wpasec myuncracked*.cap
As "bonus" you can download a list of found candidates (updated whenever a new candidate was found) direct from here:
http://wpa-sec.stanev.org/dict/cracked.txt.gz
The pre-clean option (wlancap2hcx -p) is also 100% compatible to cap2hccapx.
But keep in mind: a (pre-)cleaned cap is useless for analysis purpose!!!!