Posts: 1
Threads: 1
Joined: Sep 2016
First, off, this product has saved me a lot of time of reformatting PCs since I can not get into ex-employees PC who didn't leave me their password. Secondly, discovering and cracking into rogue access points in our corporate environment is my main use of this product.
Question I have is this: I have generated an 8 character hex file, all combinations of 1234567890ABCDEF.
When using this with oclhashcat, I specify this to use --hex-charset
I am able to crack the WPA2 with the HEX output, but how does this convert back to a human readable ascii passphrase?
Posts: 930
Threads: 4
Joined: Jan 2015
09-12-2016, 05:20 PM
(This post was last modified: 09-12-2016, 05:26 PM by royce.
Edit Reason: forgot to add --show
)
This may help:
https://hashcat.net/forum/thread-3522.html
There is also a hashcat option to show cracks (--show).
~
Posts: 87
Threads: 4
Joined: Dec 2015
(09-12-2016, 04:45 PM)abcminer Wrote: First, off, this product has saved me a lot of time of reformatting PCs since I can not get into ex-employees PC who didn't leave me their password. Secondly, discovering and cracking into rogue access points in our corporate environment is my main use of this product.
Question I have is this: I have generated an 8 character hex file, all combinations of 1234567890ABCDEF.
When using this with oclhashcat, I specify this to use --hex-charset
I am able to crack the WPA2 with the HEX output, but how does this convert back to a human readable ascii passphrase?
hi there. you are saying your wifi hotspot is encoding the ASCII chars from your password into a HEX key of length 8? for WPA2? really? - i thought hex keys would only be used for WEP and possibly WPA, but not WPA2. So to me this sounds interesting. Maybe you can clarify and/or give more details?
Posts: 5,185
Threads: 230
Joined: Apr 2010
Note that hashcat automatically switches to hex output when the password is not in the 7 bit range, so not between 0x20 and 0x80. That's important to avoid encoding problem on the shell. So, for example, if the password contains "ö" it's shown as $HEX[...] and can then be decoded with any hex decoder.
Posts: 87
Threads: 4
Joined: Dec 2015
09-12-2016, 06:42 PM
(This post was last modified: 09-12-2016, 06:49 PM by jodler303.)
thanks atom. true that, even knew about hashcat's hex input and output modes just never used 'em yet. got confused because if the length 8 AND being hex input, now it's clear. ^^ but why would i create a file for brute forcing ?b. wasn't there custom charsets for that, e.g. using charset "de" (which includes äöüß) being way smaller than full binary charset, or at least using ?b mask instead ?
Posts: 5,185
Threads: 230
Joined: Apr 2010
Absolutely. No one should use ?b unless he knows what he's doing.
Posts: 143
Threads: 9
Joined: Dec 2012
09-13-2016, 09:30 PM
(This post was last modified: 09-13-2016, 09:30 PM by magnum.
Edit Reason: typo
)
According to the specs, a WPA/WPA2 password is printable ASCII with length between 8 and 63 inclusive. Are you seeing non-ASCII somewhere?
Posts: 5,185
Threads: 230
Joined: Apr 2010
Well, it's just a specification. You know that from a technical perspective it would work, too.
Posts: 143
Threads: 9
Joined: Dec 2012
(09-14-2016, 02:45 PM)atom Wrote: Well, it's just a specification. You know that from a technical perspective it would work, too.
Sure, I'm just interested in knowing about systems that allow it. All OS/router GUI
I've tried (not many) have rejected non-ASCII.
