Please note, this is a STATIC archive of website hashcat.net from 08 Oct 2020, cach3.com does not collect or store any user information, there is no "phishing" involved.

hashcat Forum

Full Version: best way to handle spaces output/hashcat.pot
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Somewhere along the line I messed up one of my dictionary files and when I ran a combination attack this is what Im seeing.
Code:
Hash.Type......: MD5
Time.Started...: Sat Jul 27 15:44:46 2013 (14 secs)
Time.Estimated.: Sat Jul 27 16:31:54 2013 (46 mins, 42 secs)
Speed.GPU.#1...:  5186.5k/s
Recovered......: 0/5110730 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 17821696/3517701976 (0.51%)
Rejected.......: 0/17821696 (0.00%)
HWMon.GPU.#1...:  0% Util, 47c Temp, 36% Fan

deadbeefdeadbeefdeadbeefdeadbeef:       hamburger

deadbeef and hamburger are a just a made up example of what the output does look like.

The question really becomes is there a way to not loose the spaces so you can feed the results back into hashcat?

Im on a linux box so I tend to use cat hashcat.pot | cut -c 34- >outputfile.words

Im pretty certain thats not the best approach since it kills both leading and trailing spaces.

Peace
(07-27-2013, 09:58 PM)liquiz Wrote: [ -> ]In case anyone is wondering thats from the https://www.korelogic.com

1. It doesn't matter where you have the hashes from (as per https://hashcat.net/forum/announcement-2.html you shouldn't post hashes here, they are indexed by search engines etc and of course linked to hashcat then)
2. If your definition of "space" includes also tabs, yes they are in there... you could always use -o and --outfile-format in first place
3. cut only does what it was asked to do, it (cut -c 34- hashcat.pot) doesn't strip anything but the hash itself
4. new version of hashcat also support this:
Code:
./oclHashcat-plus64.bin --show -o only_plain.txt --outfile-format 2 m0000.txt
5. echo -ne "\tjoconnor"|md5sum # this for instance generates one of the hashes you shouldn't have posted (unmasked)
(07-28-2013, 08:10 AM)philsmd Wrote: [ -> ]
(07-27-2013, 09:58 PM)liquiz Wrote: [ -> ]In case anyone is wondering thats from the https://www.korelogic.com

1. It doesn't matter where you have the hashes from (as per https://hashcat.net/forum/announcement-2.html you shouldn't post hashes here, they are indexed by search engines etc and of course linked to hashcat then)
2. If your definition of "space" includes also tabs, yes they are in there... you could always use -o and --outfile-format in first place
3. cut only does what it was asked to do, it (cut -c 34- hashcat.pot) doesn't strip anything but the hash itself
4. new version of hashcat also support this:
Code:
./oclHashcat-plus64.bin --show -o only_plain.txt --outfile-format 2 m0000.txt
5. echo -ne "\tjoconnor"|md5sum # this for instance generates one of the hashes you shouldn't have posted (unmasked)

Sorry about posting the solved hashes, that should be fixed now using a dummy example.

I'll take a look at how the output formatting in --outfile-format 2 comes out.

Peace