v3.30-49-g2f81532 segfault
#6
(02-01-2017, 01:56 PM)biatwc Wrote:
(02-01-2017, 12:40 PM)philsmd Wrote: If you use the git version you need to always do all of these steps:
Code:
$ make clean
$ git pull
$ make

I also think that reports like this should be directly addressed on github, not here.

Back to the problem... I can't reproduce:
Code:
$ cat original_hash_file
ive_changed_the_username:62c2efb7cb601def6b6db1d087ea9ba5
$ cat hashcat.potfile
6b6db1d087ea9ba5:S?A
62c2efb7cb601def:F7R[E|P
$ ./hashcat -m 3000 --username --show --outfile-format 2 original_hash_file
ive_changed_the_username:F7R[E|P
ive_changed_the_username:S?A

Hi, thanks for that.
Just noticed this latop is end of life Ubuntu, I'll sort that out and try again, then post on github if it still happens.

github issue here: https://github.com/hashcat/hashcat/issues/1010


Messages In This Thread
v3.30-49-g2f81532 segfault - by biatwc - 02-01-2017, 12:06 PM
RE: v3.30-49-g2f81532 segfault - by atom - 02-01-2017, 12:11 PM
RE: v3.30-49-g2f81532 segfault - by biatwc - 02-01-2017, 12:23 PM
RE: v3.30-49-g2f81532 segfault - by philsmd - 02-01-2017, 12:40 PM
RE: v3.30-49-g2f81532 segfault - by biatwc - 02-01-2017, 01:56 PM
RE: v3.30-49-g2f81532 segfault - by biatwc - 02-01-2017, 07:59 PM