Search Results
|
Post |
Author |
Forum
[asc]
|
Replies |
Views |
Posted |
|
|
Thread: hashcat v3.5.0
Post: hashcat v3.5.0
[hr]
Welcome to hashcat v3.5.0 release! This is just a smaller update, mostly bugfixes.
I recommend upgrading even if you did not face any errors with older versions.
Thanks to everyone who... |
|
atom |
hashcat
|
9 |
18,853 |
04-05-2017, 03:58 PM |
|
|
Thread: GPU temp retain trigger doesn't work
Post: RE: GPU temp retain trigger doesn't work
It depends on your OS/Distribution. I just wanted to show your it's not a hashcat issue. |
|
atom |
hashcat
|
3 |
6,709 |
04-06-2017, 09:21 AM |
|
|
Thread: hashcat v3.5.0
Post: RE: hashcat v3.5.0
It's 3.5.0 not 3.50, maybe you need to update your url generator logic. |
|
atom |
hashcat
|
9 |
18,853 |
04-06-2017, 09:21 AM |
|
|
Thread: Poor performance Mac OS and ATI Radeon HD 5870
Post: RE: Poor performance Mac OS and ATI Radeon HD 5870
The GPU is ways too old, the drivers are outdated. I'm sure you had to use --force to get it working. There's a reason why we put that flag there. Solution: Trash the GPU, buy a new one. |
|
atom |
hashcat
|
2 |
4,080 |
04-09-2017, 08:54 AM |
|
|
Thread: Linux: Amdgpupro 16.60
Post: RE: Linux: Amdgpupro 16.60
Just checked new 17.10 driver, no changes to 16.60 - all bugs still exist. Currently 16.40 is still the best amgpu-pro driver. |
|
atom |
hashcat
|
8 |
9,514 |
04-11-2017, 01:29 PM |
|
|
Thread: Hashcat Cluster
Post: RE: Hashcat Cluster
The reason is what I've described with the results of my tests if AMDGPU-Pro. The power-saving is simply too aggressive and there's no way (yet) to turn it off. |
|
atom |
hashcat
|
14 |
14,791 |
04-20-2017, 08:20 AM |
|
|
Thread: Brute-force with only half of the cipher text
Post: RE: Brute-force with only half of the cipher text
No, this is not supported. Also you'd end up with 2^(32-8) possible passwords, which is surely not what you want. |
|
atom |
hashcat
|
4 |
4,564 |
04-20-2017, 08:27 AM |
|
|
Thread: Understanding speed-only
Post: RE: Understanding speed-only
Note that --keyspace does not return the entire keyspace in case you're cracking fast hashes. It's only the base count, the amplifiers are left out and run inside the kernel. The "ms" count is the tim... |
|
atom |
hashcat
|
3 |
4,168 |
04-20-2017, 08:31 AM |
|
|
Thread: How to show username after crack
Post: RE: How to show username after crack
https://hashcat.net/wiki/doku.php?id=frequently_asked_questions#how_can_i_show_previously_cracked_passwords_and_output_them_in_a_specific_format_eg_emailpassword |
|
atom |
hashcat
|
2 |
10,506 |
04-20-2017, 08:33 AM |
|
|
Thread: using essid like aircrack-ng does
Post: RE: using essid like aircrack-ng does
If you're talking about cap2hccapx you can specify a single essid to convert. |
|
atom |
hashcat
|
2 |
3,156 |
04-22-2017, 10:09 AM |
|
|
Thread: Unicode == FUN
Post: RE: Unicode == FUN
It depends on how it's implemented. Also note that I've recently added iconv support to the latest beta which could help you loading the .hcchrmb file. |
|
atom |
hashcat
|
9 |
8,853 |
04-22-2017, 10:11 AM |
|
|
Thread: Speed drop after 3 minutes.
Post: RE: Speed drop after 3 minutes.
Because the --gpu-temp-disable |
|
atom |
hashcat
|
1 |
2,228 |
04-22-2017, 10:11 AM |
|
|
Thread: Unicode == FUN
Post: RE: Unicode == FUN
Only a fast one would makes sense. |
|
atom |
hashcat
|
9 |
8,853 |
04-24-2017, 03:03 PM |
|
|
Thread: Increasing maximum salt length in custom kernel
Post: RE: Increasing maximum salt length in custom kerne...
If it's a custom kernel it's propably only a few hashes to crack, in this case you can simply hardcode the salt values into the kernel. |
|
atom |
hashcat
|
3 |
3,477 |
05-07-2017, 07:49 PM |
|
|
Thread: 8-12% drop in speed in "Hashcat 3.5.0" (running wpa2)
Post: RE: 8-12% drop in speed in "Hashcat 3.5.0" (runnin...
You can "reset to hccap" the way how hashcat is working by using --nonce-error-corrections=0 |
|
atom |
hashcat
|
3 |
4,718 |
05-07-2017, 08:02 PM |
|
|
Thread: example0 failed
Post: RE: example0 failed
Looks like a problem when hashcat tries to access some of the files. This is not related to libXNVCtrl, the difference to 3.0.0 is that this version did not had a file check on startup. So maybe you'r... |
|
atom |
hashcat
|
3 |
6,767 |
05-07-2017, 08:04 PM |
|
|
Thread: ASCII encoded SHA256
Post: RE: ASCII encoded SHA256
Is the return of sha256(password) in binary? What is ascii()? |
|
atom |
hashcat
|
1 |
2,986 |
05-07-2017, 08:05 PM |
|
|
Thread: --show step too slow using large file
Post: RE: --show step too slow using large file
The problem here is the --username switch. This causes hashcat to allocate a large memory block for each hash. If you have 100 million, it will take years. So the solution would be to not use --userna... |
|
atom |
hashcat
|
3 |
4,270 |
05-07-2017, 08:07 PM |
|
|
Thread: Check for collision of the first few chars
Post: RE: Check for collision of the first few chars
You need to modify the kernel |
|
atom |
hashcat
|
1 |
2,274 |
05-07-2017, 08:08 PM |
|
|
Thread: Increasing maximum salt length in custom kernel
Post: RE: Increasing maximum salt length in custom kerne...
The maximum block size for 32 bit based sha* versions is 64 and 128 for the 64 bit based ones. So in case you want to compute a sha1 of an input message of length 102 you need to split them in two par... |
|
atom |
hashcat
|
3 |
3,477 |
05-13-2017, 02:20 PM |