v3.30-49-g2f81532 segfault - Printable Version

v3.30-49-g2f81532 segfault - Printable Version

+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Support (https://hashcat.net/forum/forum-3.html)
+--- Forum: hashcat (https://hashcat.net/forum/forum-45.html)
+--- Thread: v3.30-49-g2f81532 segfault (/thread-6250.html)

v3.30-49-g2f81532 segfault - biatwc - 02-01-2017

Hi

I've just cracked an LM hash and get a segfault when I do this:

Code:
./hashcat -m 3000 --username --show --outfile-format 2 --potfile-path hashcat.potfile ../original_hash_file

user1:F7R[E|P

Segmentation fault (core dumped)

Code:
./hashcat -V

v3.30-49-g2f81532

original_hash_file:
ive_changed_the_username:62c2efb7cb601def6b6db1d087ea9ba5

hashcat.potfile:
6b6db1d087ea9ba5:S?A
62c2efb7cb601def:F7R[E|P

System:
Linux laptop 3.19.0-79-generic #87-Ubuntu SMP Tue Dec 20 19:27:48 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu Vivid (I think)

Code:
user@laptop:~/Downloads/hashcat$ ldd hashcat

 linux-vdso.so.1 =>  (0x00007ffe7bdd4000)

libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f14644b6000)

libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f14642b2000)

libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f1463ee7000)

/lib64/ld-linux-x86-64.so.2 (0x000055e471f70000)

RE: v3.30-49-g2f81532 segfault - atom - 02-01-2017

Please try to reproduce with latest beta (88) and report back

RE: v3.30-49-g2f81532 segfault - biatwc - 02-01-2017

(02-01-2017, 12:11 PM)atom Wrote: Please try to reproduce with latest beta (88) and report back

Same output as before, I tried with master from git

RE: v3.30-49-g2f81532 segfault - philsmd - 02-01-2017

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

RE: v3.30-49-g2f81532 segfault - biatwc - 02-01-2017

(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.

RE: v3.30-49-g2f81532 segfault - biatwc - 02-01-2017

(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