Search Results
|
Post |
Author |
Forum |
Replies |
Views |
Posted
[asc]
|
|
|
Thread: v3.30-49-g2f81532 segfault
Post: RE: v3.30-49-g2f81532 segfault
biatwc Wrote: (02-01-2017, 01:56 PM)
--
philsmd Wrote: (02-01-2017, 12:40 PM)
--
If you use the git version you need to always do all of these steps:
Code:
--
$ make clean
$ git pull
$ make
... |
|
biatwc |
hashcat
|
5 |
15,575 |
02-01-2017, 07:59 PM |
|
|
Thread: v3.30-49-g2f81532 segfault
Post: RE: v3.30-49-g2f81532 segfault
philsmd Wrote: (02-01-2017, 12:40 PM)
--
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 ... |
|
biatwc |
hashcat
|
5 |
15,575 |
02-01-2017, 01:56 PM |
|
|
Thread: v3.30-49-g2f81532 segfault
Post: RE: v3.30-49-g2f81532 segfault
atom Wrote: (02-01-2017, 12:11 PM)
--
Please try to reproduce with latest beta (88) and report back
--
Same output as before, I tried with master from git |
|
biatwc |
hashcat
|
5 |
15,575 |
02-01-2017, 12:23 PM |
|
|
Thread: v3.30-49-g2f81532 segfault
Post: v3.30-49-g2f81532 segfault
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:F7... |
|
biatwc |
hashcat
|
5 |
15,575 |
02-01-2017, 12:06 PM |