+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Announcements (https://hashcat.net/forum/forum-14.html)
+--- Forum: hashcat (https://hashcat.net/forum/forum-16.html)
+--- Thread: hashcat v4.2.0 (/thread-7711.html)
Pages:
1
2
hashcat v4.2.0 - atom - 08-02-2018
Welcome to hashcat v4.2.0!
Download binaries or sources: https://hashcat.net/hashcat/
This release is mostly about expanding support for new algorithms and fixing bugs:
- Added hash-mode 16700 = FileVault 2
- Added hash-mode 16800 = WPA-PMKID-PBKDF2
- Added hash-mode 16801 = WPA-PMKID-PMK
- Added hash-mode 16900 = Ansible Vault
Thanks to @hops_ch for contributing the Ansible Vault mode!
Improvements:
- Added JtR-compatible support for hex notation in the rules engine
- Added OpenCL device utilization to the status information in machine-readable output
- Added missing NV Tesla and Titan GPU details to tuning database
- General file handling: Abort if a byte-order mark (BOM) is detected in a wordlist, hashlist, maskfile or rulefile
- HCCAPX management: Use advanced hints in message_pair stored by hcxtools about endian bitness of replay counter
- OpenCL kernels: Abort session if kernel self-test fails
- OpenCL kernels: Add '-pure' prefix to kernel filenames to avoid problems caused by reusing existing hashcat installation folder
- OpenCL kernels: Removed the use of 'volatile' keyword in inline assembly instructions where it is not needed
- OpenCL kernels: Switched array pointer types in function declarations in order to be compatible with OpenCL 2.0
- Refactored code for --progress-only and --speed-only calculation
- SIP cracking: Increased the nonce field to allow a salt of 1024 bytes
- TrueCrypt/VeraCrypt cracking: Do an entropy check on the TC/VC header on start
- The removal of 'volatile' keyword has a large positive impact on cracking performance on macOS
- The refactored code for --progress-only is important if hashcat is used in combination with a distributed overlay such as hashtopolis
Fixed Bugs:
- Fixed a function declaration attribute in -m 8900 kernel that led to unusable -m 9300 (which shares kernel code with -m 8900)
- Fixed a miscalculation in --progress-only mode output for extremely slow kernels like -m 14800
- Fixed a missing check for errors on OpenCL devices leading to invalid removal of the restore file
- Fixed a missing kernel in -m 5600 in combination with -a 3 and -O if mask is >= 16 characters
- Fixed detection of AMD_GCN version when the rocm driver is used
- Fixed missing code section in -m 2500 and -m 2501 to crack corrupted handshakes with a LE endian bitness base
- Fixed a missing check for hashmodes using OPTS_TYPE_PT_UPPER causing the self-test to fail when using combinator and hybrid modes
- atom
RE: hashcat v4.2.0 - kevtheskin - 08-03-2018
Hello Atom , I cant see the new release ? Thanks for the update Kev
RE: hashcat v4.2.0 - DanielG - 08-03-2018
the links are https://hashcat.net/files/hashcat-4.2.0.7z and https://hashcat.net/files/hashcat-4.2.0.tar.gz
RE: hashcat v4.2.0 - wakawaka - 08-03-2018
will be interesting to try out
Added hash-mode 16800 = WPA-PMKID-PBKDF2
Added hash-mode 16801 = WPA-PMKID-PMK
RE: hashcat v4.2.0 - Mem5 - 08-03-2018
Awesome, thank you atom and all the tema behind.
RE: hashcat v4.2.0 - atom - 08-03-2018
(08-03-2018, 09:10 AM)wakawaka Wrote: will be interesting to try out
Added hash-mode 16800 = WPA-PMKID-PBKDF2
Added hash-mode 16801 = WPA-PMKID-PMK
I hope we can publish details in the next days.
RE: hashcat v4.2.0 - atom - 08-03-2018
(08-03-2018, 12:14 AM)kevtheskin Wrote: Hello Atom , I cant see the new release ? Thanks for the update Kev
Press shift+f5 on the main page eventually
RE: hashcat v4.2.0 - ccprime - 08-04-2018
Where is the 'Thanks' button
RE: hashcat v4.2.0 - hash93 - 08-04-2018
The newest version will not do my benchmark after hashmode 2500. I did the clean uninstall drivers (DDU) in safemode but no change:
Code:
PS C:\hashcat-4.2.0> .\hashcat64.exe -b
hashcat (v4.2.0) starting in benchmark mode...
Benchmarking uses hand-optimized kernel code by default.
You can use it in your cracking session by setting the -O option.
Note: Using optimized kernel code limits the maximum supported password length.
To disable the optimized kernel code in benchmark mode, use the -w option.
OpenCL Platform #1: Advanced Micro Devices, Inc.
================================================
* Device #1: Tonga, 3264/4096 MB allocatable, 28MCU
Benchmark relevant options:
===========================
* --optimized-kernel-enable
Hashmode: 0 - MD5
Speed.Dev.#1.....: 6702.0 MH/s (69.15ms) @ Accel:512 Loops:128 Thr:256 Vec:1
Hashmode: 100 - SHA1
Speed.Dev.#1.....: 2358.3 MH/s (49.14ms) @ Accel:256 Loops:64 Thr:256 Vec:1
Hashmode: 1400 - SHA-256
Speed.Dev.#1.....: 1031.8 MH/s (56.28ms) @ Accel:128 Loops:64 Thr:256 Vec:1
Hashmode: 1700 - SHA-512
Speed.Dev.#1.....: 223.7 MH/s (65.07ms) @ Accel:64 Loops:32 Thr:256 Vec:1
Hashmode: 2500 - WPA-EAPOL-PBKDF2 (Iterations: 4096)
PS C:\hashcat-4.2.0>Update: Reverted driver 17.11.4 and is working now.
RE: hashcat v4.2.0 - kevtheskin - 08-04-2018
Hello Atom,
I think the new revision has solved my speed issue. Pc has been running a wpa session for over an hour and no speed loss so far
.Thanks Kev