01-06-2020, 10:59 PM
Thank you for your help.
I exported and converted the correct handshake so I don't think that was the problem.
I have attached a cap file (the old hashcat test cap from this site) and the resulting hccap file so you can see what happens. The password is hashcat!
I suggest if converting to hccap is not reliable then perhaps it might be time to remove the option to convert to hccap? I worry people may be working on hccap's which will never crack.
I understand I am in the minority needing to use hccap.
wlanhcxinfo was used on hccapx not hccap when I experienced the none output issue when using "-o"
The file extension for the attachment is .7z, I had to call it .txt because zipped attachments would not upload.
I exported and converted the correct handshake so I don't think that was the problem.
I have attached a cap file (the old hashcat test cap from this site) and the resulting hccap file so you can see what happens. The password is hashcat!
I suggest if converting to hccap is not reliable then perhaps it might be time to remove the option to convert to hccap? I worry people may be working on hccap's which will never crack.
I understand I am in the minority needing to use hccap.
wlanhcxinfo was used on hccapx not hccap when I experienced the none output issue when using "-o"
The file extension for the attachment is .7z, I had to call it .txt because zipped attachments would not upload.