Hashcat 5.1 beta output format incorrectly displayed
#1
The format is displayed incorrectly:
3 | hash [: salt]: plain
Thanks.
Reply
#2
the format changed with https://github.com/hashcat/hashcat/pull/2292 (requested here: https://github.com/hashcat/hashcat/issues/2255).

The --help output should reflect the new format that should be used:
Code:
--outfile-format           | Str  | Outfile format to use, separated with commas
Reply
#3
We have:
  1 | hash [: salt]
   2 | plain
   3 | hex_plain
   4 | crack_pos
   5 | timestamp absolute
   6 | timestamp relative
We type:
--outfile-format = 1,2
I get the desired result.
Many thanks.
Reply
#4
that's by the way the default format... you only need to use --outfile-format parameter if it is different from "1,2"
Reply
#5
(03-19-2020, 01:39 PM)philsmd Wrote: that's by the way the default format... you only need to use --outfile-format parameter if it is different from "1,2"

Default 1.3
Reply
#6
What is the hash type that you are using ? What's the hashcat version (try with https://hashcat.net/beta) ?

The default with 1,2 is to use "$HEX[" and the hexadecimal chars and "]" at the end if the password contains the separator character (":") or non-printable bytes.

With 1,3 you do not have the "$HEX[" , nor "]", within the output . They are very different.

Please test again and explain exactly what you do/run and what you see. Thanks
Reply
#7
(03-19-2020, 04:06 PM)philsmd Wrote: What is the hash type that you are using ? What's the hashcat version (try with https://hashcat.net/beta) ?
I use to hack WPA.
It is about this latest version that we are talking about.
Here is the contents of the .exe file:
[url=[Image: 844e9ecd419dbd8b9d8311662b2aa28c.jpg]][/url]
Reply
#8
Yeah, but that is not the default value, but just an example within the --help:
Code:
Options Short / Long | Type | Description | Example

it clearly says, that it is an Example . The default value is still 1,2
Reply
#9
Yes!!! You're right.
Thank you very much for your perseverance.
Reply