hi im replacing all the specs on my pc and am wondering if the MSI Radeon RX 6600 XT 8 GB MECH 2X OC Video Card would preform well with hash cat and if its worth getting if not what would your recommend

hi im thinking of getting the ASUS TUF GAMING FX505DT-BQ051T AMD Ryzen 5 8GB RAM 512GB SSD 15.6 Laptop do you guys think this laptop would work well with hashcat?

Hello everyone! I have confused with hashcat speed of this attack mode.
Look. I created my own script for generating passwords. Everything working fine, password successfully restored. But I have problems with speed, which magically decrease in 1000x. Depence on which side dict is.

Full command: hashcat -a 1 -m 26600 -d 1 -w 4 $metamask$hash credentials.txt rules/main.dict. (and hashcat -a 1 -m 26600 -d 1 -w 4 $metamask$hash rules/main.dict credentials.txt also).

So yes, I found that this mode only connect right side, not both. So I decided to mix dictionaries manually. Look at the difference in speed:



null
null

So the questions:
1) Why this is happens?
2) Am I miss any flag that can ask hashcat to combinate "/rules/main.dict" in start and end?
3) If there is no solution to combinate in start and end of password and I forced to run hashcat two times, can I fix this difference in speed?


Thank you very much for your knowledge and your time!

  left side.png (Size: 212.6 KB / Downloads: 6)

  right side.png (Size: 91.98 KB / Downloads: 8)

Hi,

I am trying to get a DL380 Gen 8 with 4 x E5-4640 0 @ 2.40GHz working with hashcat under Linux 20.04LTS.

I have successfully installed “Intel® CPU Runtime for OpenCL™ Applications 18.1 for Linux* OS (64bit only)” and it sees my Intel CPUs but "clinfo" hangs when I run it. Also, when I try and run hashcat I receive an "clCreateContext(): CL_DEVICE_NOT_AVAILABLE " and also Device #1 "skipped"?

Any ideas what is wrong/missing?

thanks

ubuntu@ubuntu:~/hashcat/hashcat-6.2.4$ hashcat -I                                                                                               
hashcat (v5.1.0) starting...                                                                                                                             
                                                                                                                                                         
OpenCL Info:                                                                                                                                             
                                                                                                                                                         
Platform ID #1                                                                                                                                           
  Vendor  : Intel(R) Corporation                                                                                                                         
  Name    : Intel(R) CPU Runtime for OpenCL(TM) Applications                                                                                             
  Version : OpenCL 2.1 LINUX                                                                                                                             
                                                                                                                                                         
  Device ID #1                                                                                                                                           
    Type          : CPU                                                                                                                                 
    Vendor ID      : 8                                                                                                                                   
    Vendor        : Intel(R) Corporation                                                                                                                 
    Name          : Intel(R) Xeon(R) CPU E5-4640 0 @ 2.40GHz                                                                                             
    Version        : OpenCL 2.1 (Build 0)                                                                                                                 
    Processor(s)  : 64                                                                                                                                   
    Clock          : 2400                                                                                                                                 
    Memory        : 16089/64359 MB allocatable                                                                                                           
    OpenCL Version : OpenCL C 2.0                                                                                                                         
    Driver Version : 18.1.0.0920   



ubuntu@ubuntu:~/hashcat/hashcat-6.2.4$ ./hashcat.bin -m 0 -t 32 -a 7 --opencl-device-type 1 example0.hash ?a?a?a?a | more                                 
hashcat (v6.2.4) starting                                                                                                                                 
                                                                                                                                                         
clCreateContext(): CL_DEVICE_NOT_AVAILABLE                                                                                                               
                                                                                                                                                         
OpenCL API (OpenCL 2.1 LINUX) - Platform #1 [Intel(R) Corporation]                                                                                       
==================================================================                                                                                       
* Device #1: Intel(R) Xeon(R) CPU E5-4640 0 @ 2.40GHz, skipped                                                                                           
                                                                                                                                                         
Minimum password length supported by kernel: 0                                                                                                           
Maximum password length supported by kernel: 256     

clinfo:


Number of platforms                              1                                                                                                       
  Platform Name                                  Intel(R) CPU Runtime for OpenCL(TM) Applications                                                          Platform Vendor                                Intel(R) Corporation                                                                                      Platform Version                                OpenCL 2.1 LINUX                                                                                          Platform Profile                                FULL_PROFILE                                                                                              Platform Extensions                            cl_khr_icd cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_depth_images cl_khr_3d_image_writes cl_intel_exec_by_local_thread cl_khr_spir cl_khr_fp64 cl_khr_image2d_from_buffer cl_intel_vec_len_hint                                                                                                         
  Platform Host timer resolution                  1ns                                                                                                     
  Platform Extensions function suffix            INTEL                                                                                                                                                                                                                                       
  Platform Name                                  Intel(R) CPU Runtime for OpenCL(TM) Applications                                                             
Number of devices                                1                                                                                                          Device Name                                    Intel(R) Xeon(R) CPU E5-4640 0 @ 2.40GHz                                                             
  Device Vendor                                  Intel(R) Corporation                                                                                      Device Vendor ID                                0x8086                                                                                                    Device Version                                  OpenCL 2.1 (Build 0)                                                                                      Driver Version                                  18.1.0.0920                                                                                             
  Device OpenCL C Version                        OpenCL C 2.0                                                                                           
  Device Type                                    CPU                                                                                                     
  Device Profile                                  FULL_PROFILE                                                                                           
  Device Available                                Yes                                                                                                     
  Compiler Available                              Yes                                                                                                     
  Linker Available                                Yes                                                                                                     
  Max compute units                              64                                                                                                     
  Max clock frequency                            2400MHz                                                                                                 
  Device Partition                                (core)                                                                                                 
    Max number of sub-devices                    64                                                                                                     
    Supported partition types                    by counts, equally, by names (Intel)                                                                   
    Supported affinity domains                    (n/a)                                                                                                   
  Max work item dimensions                        3                                                                                                       
  Max work item sizes                            8192x8192x8192                                                                                         
  Max work group size                            8192                                                                                                   
  Preferred work group size multiple              <getWGsizes:1171: create context : error -2>                                                           
  Max sub-groups per work group                  1                                                                                                       
  Preferred / native vector sizes                                                                                                                         
    char                                                1 / 16                                                                                           
    short                                                1 / 8                                                                                           
    int                                                  1 / 4                                                                                           
    long                                                1 / 2                                                                                           
    half                                                0 / 0        (n/a)                                                                               
    float                                                1 / 8                                                                                           
    double                                              1 / 4        (cl_khr_fp64)                                                                       
  Half-precision Floating-point support          (n/a)                                                                                                   
  Single-precision Floating-point support        (core)                                                                                                 
    Denormals                                    Yes                                                                                                     
    Infinity and NANs                            Yes                                                                                                     
    Round to nearest                              Yes                                                                                                     
    Round to zero                                No                                                                                                     
    Round to infinity                            No                                                                                                     
    IEEE754-2008 fused multiply-add              No                                                                                                     
    Support is emulated in software              No                                                                                                     
    Correctly-rounded divide and sqrt operations  No                                                                                                     
  Double-precision Floating-point support        (cl_khr_fp64)                                                                                           
    Denormals                                    Yes                                                                                                     
    Infinity and NANs                            Yes                                                                                                     
    Round to nearest                              Yes                                                                                                     
    Round to zero                                Yes                                                                                                     
    Round to infinity                            Yes                                                                                                     
    IEEE754-2008 fused multiply-add              Yes                                                                                                     
    Support is emulated in software              No                                                                                                     
  Address bits                                    64, Little-Endian                                                                                       
  Global memory size                              67485503488 (62.85GiB)                                                                                 
  Error Correction support                        No                                                                                                     
  Max memory allocation                          16871375872 (15.71GiB)                                                                                 
  Unified memory for Host and Device              Yes                                                                                                     
  Shared Virtual Memory (SVM) capabilities        (core)                                                                                                 
    Coarse-grained buffer sharing                Yes                                                                                                     
    Fine-grained buffer sharing                  Yes                                                                                                     
    Fine-grained system sharing                  Yes                                                                                                     
    Atomics                                      Yes                                                                                                     
  Minimum alignment for any data type            128 bytes                                                                                               
  Alignment of base address                      1024 bits (128 bytes)                                                                                   
  Preferred alignment for atomics                                                                                                                         
    SVM                                          64 bytes                                                                                               
    Global                                        64 bytes                                                                                               
    Local                                        0 bytes                                                                                                 
  Max size for global variable                    65536 (64KiB)                                                                                           
  Preferred total size of global vars            65536 (64KiB)                                                                                           
  Global Memory cache type                        Read/Write                                                                                             
  Global Memory cache size                        262144 (256KiB)                                                                                         
  Global Memory cache line size                  64 bytes                                                                                               
  Image support                                  Yes                                                                                                     
    Max number of samplers per kernel            480                                                                                                     
    Max size for 1D images from buffer            1054460992 pixels                                                                                       
    Max 1D or 2D image array size                2048 images                                                                                             
    Base address alignment for 2D image buffers  64 bytes                                                                                               
    Pitch alignment for 2D image buffers          64 pixels                                                                                               
    Max 2D image size                            16384x16384 pixels                                                                                     
    Max 3D image size                            2048x2048x2048 pixels                                                                                   
    Max number of read image args                480                                                                                                     
    Max number of write image args                480                                                                                                     
    Max number of read/write image args          480                                                                                                     
  Max number of pipe args                        16                                                                                                     
  Max active pipe reservations                    4095                                                                                                   
  Max pipe packet size                            1024         
  Global Memory cache type                        Read/Write                                                                                             
  Global Memory cache size                        262144 (256KiB)                                                                                         
  Global Memory cache line size                  64 bytes                                                                                               
  Image support                                  Yes                                                                                                     
    Max number of samplers per kernel            480                                                                                                     
    Max size for 1D images from buffer            1054460992 pixels                                                                                       
    Max 1D or 2D image array size                2048 images                                                                                             
    Base address alignment for 2D image buffers  64 bytes                                                                                               
    Pitch alignment for 2D image buffers          64 pixels                                                                                               
    Max 2D image size                            16384x16384 pixels                                                                                     
    Max 3D image size                            2048x2048x2048 pixels                                                                                   
    Max number of read image args                480                                                                                                     
    Max number of write image args                480                                                                                                     
    Max number of read/write image args          480                                                                                                     
  Max number of pipe args                        16                                                                                                     
  Max active pipe reservations                    4095                                                                                                   
  Max pipe packet size                            1024                                                                                                   
  Local memory type                              Global                                                                                                 
  Local memory size                              32768 (32KiB)                                                                                           
  Max number of constant args                    480                                                                                                     
  Max constant buffer size                        131072 (128KiB)                                                                                         
  Max size of kernel argument                    3840 (3.75KiB)                                                                                         
  Queue properties (on host)                                                                                                                             
    Out-of-order execution                        Yes                                                                                                     
    Profiling                                    Yes                                                                                                     
    Local thread execution (Intel)                Yes                                                                                                     
  Queue properties (on device)                                                                                                                           
    Out-of-order execution                        Yes                                                                                                     
    Profiling                                    Yes                                                                                                     
    Preferred size                                4294967295 (4GiB)                                                                                       
    Max size                                      4294967295 (4GiB)                                                                                       
  Max queues on device                            4294967295                                                                                             
  Max events on device                            4294967295                                                                                             
  Prefer user sync for interop                    No                                                                                                     
  Profiling timer resolution                      1ns                                                                                                     
  Execution capabilities                                                                                                                                 
    Run OpenCL kernels                            Yes                                                                                                     
    Run native kernels                            Yes                                                                                                     
    Sub-group independent forward progress        No                                                                                                     
    IL version                                    SPIR-V_1.0                                                                                             
    SPIR versions                                1.2                                                                                                     
  printf() buffer size                            1048576 (1024KiB)                                                                                       
  Built-in kernels                                (n/a)                                                                                                   
  Device Extensions                              cl_khr_icd cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_depth_images cl_khr_3d_image_writes cl_intel_exec_by_local_thread cl_khr_spir cl_khr_fp64 cl_khr_image2d_from_buffer cl_intel_vec_len_hint     
<<<**** HANGS HERE *****>>>

Hi!

"What is the current stable version of hashcat?"

According to Hashcat announcements forum it's 6.2.0:
https://hashcat.net/forum/forum-16.html

According to Hashcat Wikipedia article it's 6.2.4:
https://en.wikipedia.org/wiki/Hashcat

According to Hashcat download page it's 6.2.5:
https://hashcat.net/hashcat/


This question comes up when signing up for an account on these forums. What am I supposed to type in as the answer?

I tried "6.2.5", "6.2.4" and I just tried "6.2.0". I even tried "v6.2.5", "hashcat v6.2.5" as it's typed out on the download page, and I even went as far as pasting in MD5 hash values of these strings. None of which worked.

If you can't share this secret publicly, can someone send me a PM with the correct answer to the question? Alternatively, can you tell me if the full version number is expected, and if it contains any letters?

Playfully yours,
meow
🐈

Hi!

Forum rules say:
"Do not post issues about using a GPU that is no longer supported by the latest driver from its vendor."
https://hashcat.net/forum/announcement-2.html

So I would like to start off by establishing if GTX 560 Ti is supported or not by the current version of Hashcat.

By "vendor" you mean Nvidia, right?

I have this GPU:
https://www.asus.com/SupportOnly/ENGTX56..._Download/

Latest driver available there is version 306.23 from Oct 25, 2012.

I looked at the Nvida driver download page I find newer drivers:
https://www.nvidia.com/en-us/geforce/drivers/

They have version 391.35 from Mar 27, 2018.

That's still 3 years too old for Hashcat to support it?

I also wonder if it's possible that the same GPU is still supported on Linux based OSes if the vendor is not Nvidia and is still maintained? I am running Windows on it.

I also looked at the "Is your card supported" sticky thread:
https://hashcat.net/forum/thread-919.html

Following the link for Nvidia reveals a list where GTX 560 is listed as having "Compute Capability" of version "2.0". What does that tell me? It has CUDA cores?... I know it has CUDA cores, 384 of them, not many by today's measure but it still does have them.

"Is your card supported"... in what sense? This question is ill-defined. Yes, GTX 560 Ti does have CUDA support if that's what you're after, but the real question is if it's supported by Hashcat! None of those links lead to answers of such questions.

I didn't look closer at the GitHub link for AMD GPUs as it seems to be programming related rather than displaying what AMD GPUs are compatible with Hashcat, and in that sense, it's the same as the Nvidia link displaying what Nvidia GPUs are CUDA compatible. That sticky alone is as old as GTX 560 itself, I don't see how that's helpful at all (someone please fill me in), other than showing you if your GPU got CUDAs, in hope that Hashcat of the time had support for your model so you could leverage good hash(-ish) performance.

Do you have a list of your own that clearly indicates what GPU cards are supported by Hashcat? A compatibility chart with Hashcat version numbers would be very helpful.

I could go on and download an old version of Hashcat to see if that works better with my GPU. It's just that there are so many versions, it would be helpful to be able to narrow it down a little, and the issue may not be related to GPU drivers anyway (the rule is presuming that the issue is related to outdated driver). So for that reason I am reluctant to go down this rabbit hole, it's not that I am lazy. But thanks to this clearly defined rule, I have hit a road block before I had the chance to tell you what the problem is that I'm having with this GPU. So it seems I won't be able to ask for help with Hashcat on Hashcat forums, not until I upgrade my GPU to something more recent, in which case I may not need your help at all.

Playfully yours,
meow
🐈

hi, guys i am new here

i forgot my password but i have an idea of my password so bitgo gave me some data and say i must try to bruite force the pass now i am stuck with the data i got from bitgo since i dont know which one to use so please anyone who can help how i can excecute this into hashcat please help i will give example of the data below.

here you go:  {
    "iv":"qdsZZWoUK/WKmcPLzrBUhg==",
    "v":1,
    "iter":10000,
    "ks":256,
    "ts":64,
    "mode":"ccm",
    "adata":"",
    "cipher":"aes",
    "salt":"j4VpR8Rqag0=",
    "ct":"z12cqlIJ8UjZMTrr9Sne9eGHkmC7VG8tcdOTTND+PJFL2DDCKAw5+tuv0Oc7e6mB//ee6cFbPed7KAl5fH6mQeLaJi6uChEcfNwOOMsGJn1mhxM0+yT7R4POGilQxapEZsi7vdG6lkjX4dOk81M4okAeRJ6hxbjA="
}

I've been trying to figure this out for hours the definite issue is I'm getting, "Time out is not disabled". I understand it needs the patch but I can't figure out how to do it at least not in a way I feel safe trying so if someone could explain that to me step by step or send me a link I would be very grateful.
I'm not going  to bother wasting your time with all the specs because they are in the field in the screenshots except for I'm using an AMD 3700X CPU and Windows 11.
My old rig had a 2070Super and was running in MH/s the 3070 is running KH/s I can't figure out the reason for any of these issues. With the 2070 Super I installed Cuda and I was golden but this one has the problem I mentioned and I'm getting: 

Optimized kernel requested but not available or not required. Falling back to pure kernel 

I don't have any idea if that's good or bad. The last thing Hashcat is seeing my GPU as two and I only have one. If I use -d 1 it runs but with very little memory. If I run -d 2 it says, "Please be patient" and never does anything.

PS C:\Users\jacki>PS C:\hashcat-6.2.5> .\hashcat  -m 22000 wlan13.16800 H:\Wordlists -a 0 -w 4 -O
hashcat (v6.2.5) starting

* Device #1: WARNING! Kernel exec timeout is not disabled.
            This may cause "CL_OUT_OF_RESOURCES" or related errors.
            To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #2: WARNING! Kernel exec timeout is not disabled.
            This may cause "CL_OUT_OF_RESOURCES" or related errors.
            To disable the timeout, see: https://hashcat.net/q/timeoutpatch
CUDA API (CUDA 11.5)
====================
* Device #1: NVIDIA GeForce RTX 3070, 7132/8191 MB, 46MCU

OpenCL API (OpenCL 3.0 CUDA 11.5.121) - Platform #1 [NVIDIA Corporation]
========================================================================
* Device #2: NVIDIA GeForce RTX 3070, skipped

Kernel ./OpenCL/m22000-optimized.cl:
Optimized kernel requested, but not available or not required
Falling back to pure kernel

Minimum password length supported by kernel: 8
Maximum password length supported by kernel: 63

Hashes: 8 digests; 8 unique digests, 5 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1

Optimizers applied:
* Zero-Byte
* Slow-Hash-SIMD-LOOP

Watchdog: Temperature abort trigger set to 90c

INFO: Removed 2 hashes found as potfile entries or as empty hashes.

Host memory required for this attack: 1464 MB

Dictionary cache hit:
* Filename..: H:\Wordlists/1.txt
* Passwords.: 14344385
* Bytes.....: 139921511
* Keyspace..: 14344385

[s]tatus [p]ause ypass [c]heckpoint [f]inish [q]uit =>

Session..........: hashcat
Status...........: Running
Hash.Mode........: 22000 (WPA-PBKDF2-PMKID+EAPOL)
Hash.Target......: wlan13.16800
Time.Started.....: Wed Dec 08 09:01:33 2021 (34 secs)
Time.Estimated...: Wed Dec 08 09:02:46 2021 (39 secs)
Kernel.Feature...: Pure Kernel
Guess.Base.......: File (H:\Wordlists/1.txt)
Guess.Queue......: 1/7 (14.29%)
Speed.#1.........:  643.8 kH/s (279.87ms) @ Accel:64 Loops:512 Thr:512 Vec:1
Recovered........: 2/8 (25.00%) Digests, 1/5 (20.00%) Salts
Progress.........: 39499878/71721925 (55.07%)
Rejected.........: 15382630/39499878 (38.94%)
Restore.Point....: 7005347/14344385 (48.84%)
Restore.Sub.#1...: Salt:2 Amplifier:0-1 Iteration:0-1
Candidate.Engine.: Device Generator
Candidates.#1....: jillian13! -> chowderstick
Hardware.Mon.#1..: Temp: 61c Fan: 67% Util:100% Core:1979MHz Mem:6993MHz Bus:16

Approaching final keyspace - workload adjusted.

I tried doing what it says but then it wont use the driver that I install as per Hashcat forum all I can find is the newest and Hashcat says that 7.5 isn't supported use 7.4. I had this problem last night but I rolled everything back and I thought it was fixed but as you can see it's not. If I run it with -d 2 it says be patient and doesn't do anything -d 1 or not using -d it fails.
For the temperature I put the fan on 100% and it holds steady at 53, but I keep getting the temperature warning. When I get it I was hitting S  immediately to see the temp. Then I opened the GPU monitor just in case and it's not showing anything near 65 so I'm not sure what's going on there. It will throw the warning up four or more times one after the other real fast then it stops until I start another session.

Session..........: hashcat
Status...........: Exhausted
Hash.Mode........: 22000 (WPA-PBKDF2-PMKID+EAPOL)
Hash.Target......: wlan13.16800
Time.Started.....: Wed Dec 08 09:01:33 2021 (1 min, 2 secs)
Time.Estimated...: Wed Dec 08 09:02:35 2021 (0 secs)
Kernel.Feature...: Pure Kernel
Guess.Base.......: File (H:\Wordlists/1.txt)
Guess.Queue......: 1/7 (14.29%)
Speed.#1.........:  637.1 kH/s (169.67ms) @ Accel:64 Loops:512 Thr:512 Vec:1
Recovered........: 2/8 (25.00%) Digests, 1/5 (20.00%) Salts
Progress.........: 71721925/71721925 (100.00%)
Rejected.........: 23674565/71721925 (33.01%)
Restore.Point....: 14344385/14344385 (100.00%)
Restore.Sub.#1...: Salt:4 Amplifier:0-1 Iteration:0-1
Candidate.Engine.: Device Generator
Candidates.#1....: $HEX[303136363032323533] -> $HEX[042a0337c2a156616d6f732103]
Hardware.Mon.#1..: Temp: 58c Fan: 68% Util: 79% Core:1979MHz Mem:6994MHz Bus:16

Dictionary cache hit:
* Filename..: H:\Wordlists/realhuman_phill.txt
* Passwords.: 63941069
* Bytes.....: 716441107
* Keyspace..: 63941069

Cracking performance lower than expected?

* Append -S to the commandline.
  This has a drastic speed impact but can be better for specific attacks.
  Typical scenarios are a small wordlist but a large ruleset.

* Update your backend API runtime / driver the right way:
  https://hashcat.net/faq/wrongdriver

* Create more work items to make use of your parallelization power:
  https://hashcat.net/faq/morework

Approaching final keyspace - workload adjusted.


Session..........: hashcat
Status...........: Exhausted
Hash.Mode........: 22000 (WPA-PBKDF2-PMKID+EAPOL)
Hash.Target......: wlan13.16800
Time.Started.....: Wed Dec 08 09:02:41 2021 (5 mins, 3 secs)
Time.Estimated...: Wed Dec 08 09:07:44 2021 (0 secs)
Kernel.Feature...: Pure Kernel
Guess.Base.......: File (H:\Wordlists/realhuman_phill.txt)
Guess.Queue......: 2/7 (28.57%)
Speed.#1.........:  619.0 kH/s (247.58ms) @ Accel:32 Loops:1024 Thr:512 Vec:1
Recovered........: 2/8 (25.00%) Digests, 1/5 (20.00%) Salts
Progress.........: 319705345/319705345 (100.00%)
Rejected.........: 85910445/319705345 (26.87%)
Restore.Point....: 63941069/63941069 (100.00%)
Restore.Sub.#1...: Salt:4 Amplifier:0-1 Iteration:0-1
Candidate.Engine.: Device Generator
Candidates.#1....: $HEX[7a7469757772737963] -> $HEX[b47461656b776f6e646f]
Hardware.Mon.#1..: Temp: 61c Fan: 70% Util: 56% Core:1979MHz Mem:6994MHz Bus:16

Dictionary cache hit:
* Filename..: H:\Wordlists/realuniq.lst
* Passwords.: 1212336035
* Bytes.....: 15696118781
* Keyspace..: 1212336035

Driver temperature threshold met on GPU #1. Expect reduced performance.
Driver temperature threshold met on GPU #1. Expect reduced performance.
Driver temperature threshold met on GPU #1. Expect reduced performance.
Driver temperature threshold met on GPU #1. Expect reduced performance.
Driver temperature threshold met on GPU #1. Expect reduced performance.
[s]tatus [p]ause ypass [c]heckpoint [f]inish [q]uit =>

Session..........: hashcat
Status...........: Running
Hash.Mode........: 22000 (WPA-PBKDF2-PMKID+EAPOL)
Hash.Target......: wlan13.16800
Time.Started.....: Wed Dec 08 09:07:51 2021 (6 mins, 2 secs)
Time.Estimated...: Wed Dec 08 11:18:10 2021 (2 hours, 4 mins)
Kernel.Feature...: Pure Kernel
Guess.Base.......: File (H:\Wordlists/realuniq.lst)
Guess.Queue......: 3/7 (42.86%)
Speed.#1.........:  616.6 kH/s (281.68ms) @ Accel:32 Loops:1024 Thr:512 Vec:1
Recovered........: 2/8 (25.00%) Digests, 1/5 (20.00%) Salts
Progress.........: 313908465/6061680175 (5.18%)
Rejected.........: 35052785/313908465 (11.17%)
Restore.Point....: 62781693/1212336035 (5.18%)
Restore.Sub.#1...: Salt:4 Amplifier:0-1 Iteration:0-1
Candidate.Engine.: Device Generator
Candidates.#1....: 25630550 -> 2605131894
Hardware.Mon.#1..: Temp: 62c Fan: 71% Util:100% Core:1979MHz Mem:6994MHz Bus:16

Driver temperature threshold met on GPU #1. Expect reduced performance.
[s]tatus [p]ause ypass [c]heckpoint [f]inish [q]uit =>

Session..........: hashcat
Status...........: Running
Hash.Mode........: 22000 (WPA-PBKDF2-PMKID+EAPOL)
Hash.Target......: wlan13.16800
Time.Started.....: Wed Dec 08 09:07:51 2021 (7 mins, 7 secs)
Time.Estimated...: Wed Dec 08 11:18:00 2021 (2 hours, 3 mins)
Kernel.Feature...: Pure Kernel
Guess.Base.......: File (H:\Wordlists/realuniq.lst)
Guess.Queue......: 3/7 (42.86%)
Speed.#1.........:  616.9 kH/s (282.51ms) @ Accel:32 Loops:1024 Thr:512 Vec:1
Recovered........: 2/8 (25.00%) Digests, 1/5 (20.00%) Salts
Progress.........: 368905085/6061680175 (6.09%)
Rejected.........: 41061245/368905085 (11.13%)
Restore.Point....: 73737952/1212336035 (6.08%)
Restore.Sub.#1...: Salt:1 Amplifier:0-1 Iteration:2-5
Candidate.Engine.: Device Generator
Candidates.#1....: 2ilovewendy2 -> 2LUSCIOUS
Hardware.Mon.#1..: Temp: 62c Fan: 70% Util:100% Core:1979MHz Mem:6994MHz Bus:16

[s]tatus [p]ause ypass [c]heckpoint [f]inish [q]uit =>

Hello. I wonder if it possible to save in a file all hashes that don't fit to our password we are looking for? Just in a format like potfiles (hash:plain password) ?

Hi guys.
I want ask about compare Hashcat performance between
this
Asus EKWB Geforce RTX 3090 24GB (RTX3090-24-EK) 
vs 
my 4xROG Strix GeForce GTX 1080 Ti OC edition 11GB
both with waterblock.
Sorry for my english
Pls tell me, can I change this new rtx3090 with my 4x gtx1080Ti?

Hello, I've got hex encoded password for 2007 excel .xlsx file (using 9400 rule). When I'm converting hex string to ascii one of symbols look like that: ê. Excel throw invalid password error. I'm using excel 2016 to open file. UTF codecs can't convert hex to text because of start byte error. My question: Is that possible to open excel with hex string? I really can't find information about it. If not possible, what you can recommend for my situation?

Good afternoon, I am writing here for the first time.

Have a question about extracting the 1password master password hash.

The situation is this: I only used 1password on my old iPhone 10 and didn’t use it on Mac / PC. I forgot my master password as I last used this iPhone in 2019.
I have access to the iPhone and iCloud, the information I need is in 1password, the secret key is entered, only the master password is needed.

Tell me how can I extract the 1password hash from the iPhone for further decryption? Thanks to all!

Hi!

So I finally did it, I robbed a bank and I purchased a brand new GPU for use with Hashcat. It's not a monster RTX model, but a modest GTX 1650. It's good enough for me, and it's much better than the GTX 560 Ti I was struggling with for the last two days.

You would think that buying a new GPU with up to date drivers will make your problems go away. Not in my case they didn't. I was still unable to run Hashcat 6.2.5.


I think I was being patient enough. I waited for 10 minutes before I aborted.

Before trying to run 6.2.5, I was running 3.0 with flying colors. I was getting up to 6500 MH/s, relying only on Open CL, no CUDA runtime. This is a huge improvement for my limited resources. An MD5 job that took 1 hour, 23 minutes and 29 seconds on GTX 560 Ti was now taking only 12 minutes and 22 seconds on GTX 1650. Compare that with 31 minutes 16 seconds on Radeon HD 6870, and 3 hour, 39 minutes and 15 seconds on Intel UHD 630. As you can see this is a big win for me.

I decided to start with 3.0 because I was having great success with that version using old GPUs. Then I moved on to 4.0 version and my hashrate started to decline, quite significantly. I was getting 470 MH/s at most. With version 5.0 I saw a good improvement, maxing it out at 1835 MH/s.

But version 6.2.5 was still beyond my reach. It doesn't work with GTX 560 Ti at all and it almost works with GTX 1650. For some reason it was failing to load  and 6.2.5 requires CUDA 11. So I downloaded and installed CUDA 11, but on top of CUDA 8. These can be installed side by side, right? I restarted the command shell and restarted Hashcat 6.25 and it worked. But with one noticeable difference, it was running at half the speed I was getting with Open CL. It is currently at work and hashing at about 3700 MH/s.

Maybe I am missing something, but isn't CUDA mode supposed to be faster than Open CL on Nvidia GPUs? That's the whole point of installing it, I presume.

Again, this is an MD5 job and it should be plow through it in mere minutes. I am using brute force mode, with a mask. I am also specifying an output file for convenience. That's it, no other options are enabled, just -a, -m, -o, hash file, and a mask.


Can someone explain to me the significance of these three info segments? Why is CUDA listed twice? How is "OpenCL 3.0 CUDA 11.5.121" CUDA different from "CUDA 11.5" CUDA? And why is the AMD CPU being skipped? Is it because it lacks iGPU? Can it still be put to work?

If Open CL API can be used to utilize CUDA, why do I have to install CUDA SDK toolkit? If Open CL is the fallback runtime like it says in the warning message, why does it not do what it says and fall back to using Open CL API for Open CL runtime rather than stalling when waiting for CUDA runtime to load? Logically, if CUDA runtime is not installed, or the wrong version is installed, the program should respond in some way or time out rather than just sitting there waiting for better times.

Please forgive me for the many questions, I don't mean to bother you, you probably have better things to do than to answer my silly noob questions. But I would greatly appreciate it if you found time to write me a line or two. At least to say hello.

Playfully yours,
meow
🐈

hy there - i´m newbie.


tried to hashcat a handshake with following comand line:


tried to bruteforce a 10 digit pw (alphanumeric) with the following comand:

hashcat.exe -m 22000 -a 3 ?u?d tiscali.hccapx ?1?1?1?1?1?1?1?1?1?1

(WPA is chaged from 2500 to 22000 - thay told me) but getting following error: Hash ´?u?d´: Separator unmatched >>> No hashes loaded was seaching the internet for a solution and also trying multile changes of comand line - dind´t find any progress

if i type it like:

hashcat.exe -m 22000 -a 3 -1?u?d tiscali.hccapx ?1?1?1?1?1?1?1?1?1?1 or
hashcat.exe -m 22000 -a 3 -1 ?u?d tiscali.hccapx ?1?1?1?1?1?1?1?1?1?1


it says: hashfile ... on line Separator unmatched


  unknown.png (Size: 175.1 KB / Downloads: 1)

Hi!



I'm using Hashcat 6.2.5 and I can't seem to find a way to combine the Restore option (--restore) with the option to run with optimized kernel (-O) on the same command line. Is this not possible at all or am I missing something like having to specify the options in a particular order? I think I have exhausted all possibilities by now.






These are some of the combinations I have tried.






According to the usage hint, options are specified after the name of the program but before the hashfile. But according to the performance hint text that comes up if your hashrate is very low, the option for optimized kernel (-O) is to be "appended", meaning specified at the end of the line.


Note that I can use the -O as well as --restore, but not in combination it would seem.

Maybe I'm missing an argument somewhere?

Playfully yours,
meow
🐈

Hi!

I'm using Hashcat 6.2.5 and I can't seem to find a way to combine the Restore option (--restore) with the option to run with optimized kernel (-O) on the same command line. Is this not possible at all or am I missing something like having to specify the options in a particular order? I think I have exhausted all possibilities by now.


These are some of the combinations I have tried.


According to the usage hint, options are specified after the name of the program but before the hashfile. But according to the performance hint text that comes up if your hashrate is very low, the option for optimized kernel (-O) is to be "appended", meaning specified at the end of the line.


Note that I can use the -O as well as --restore, but not in combination it would seem.

Maybe I'm missing an argument somewhere?

Playfully yours,
meow
🐈

Hi!

Is it just me, or are you guys also having a problem with newlines when posting new posts or editing existing posts? The problem is that the more times I edit a post to make changes or to add additional bits of information, the number of new lines increases by one newline for each newline.

Initial post:

Quote:Haxx0r ipsum headers d00dz vi infinite loop semaphore it's a feature ifdef ssh fatal strlen packet sniffer public foad bin. Data void var todo giga sql highjack cache bypass new blob injection ack baz function salt char script kiddies int class Donald Knuth. Wabbit wombat machine code rm -rf null echo *.* epoch.

Cat eof less endif injection infinite loop epoch suitably small values. Overflow crack tcp perl for headers *.* default wombat bytes giga wabbit syn worm. New packet gc ban foad fork thread socket chown over clock I'm sorry Dave, I'm afraid I can't do that ddos cache.

After editing the post once:

Quote:Haxx0r ipsum headers d00dz vi infinite loop semaphore it's a feature ifdef ssh fatal strlen packet sniffer public foad bin. Data void var todo giga sql highjack cache bypass new blob injection ack baz function salt char script kiddies int class Donald Knuth. Wabbit wombat machine code rm -rf null echo *.* epoch.


Cat eof less endif injection infinite loop epoch suitably small values. Overflow crack tcp perl for headers *.* default wombat bytes giga wabbit syn worm. New packet gc ban foad fork thread socket chown over clock I'm sorry Dave, I'm afraid I can't do that ddos cache.

After editing the post twice:

Quote:Haxx0r ipsum headers d00dz vi infinite loop semaphore it's a feature ifdef ssh fatal strlen packet sniffer public foad bin. Data void var todo giga sql highjack cache bypass new blob injection ack baz function salt char script kiddies int class Donald Knuth. Wabbit wombat machine code rm -rf null echo *.* epoch.




Cat eof less endif injection infinite loop epoch suitably small values. Overflow crack tcp perl for headers *.* default wombat bytes giga wabbit syn worm. New packet gc ban foad fork thread socket chown over clock I'm sorry Dave, I'm afraid I can't do that ddos cache.

It's quite a process to clean up all the goo between paragraphs. I click to edit in full editor, and then starting from the first line of the second paragraph, I use Shift and up arrow key to select upwards, ensuring I including the last line of the first paragraph to encompass all hidden characters, then whilst holding down Shift key, I press End key to deselect the good bit of the last line in first paragraph, and lastly I press Delete key to ensure I delete all characters to the right. Then I press Enter two times to get back to proper spacing between paragraphs, just one line worth of spacing.

Then after all that trouble, it all returns again if I edit the post once more, and this time the problem has grown on each newline by one additional newline, so it's growing. Sometimes, somehow, I manage to stop the spread and I don't know how or why, sometimes I'm just lucky I guess. It's like trying to contain a virus, and it just keeps on growing.

I thought you should know about it. I'm sorry if this is not the right place to post about it, or if I'm the only one having this issue. My OCD immediately kicks in when I see this sort of thing.

Hi, there! Is it normal? Was it expected? v6.2.5 is slower than v5.1.0

Not just slower, but about 200 times slower! Of course, with my specific hardware/software/hash.
I am new to Hashcat. I'm using Windows and a 10-year-old laptop with an Intel Celeron CPU and an Intel GPU.
This CPU is a 3rd generation Intel processor, codename IvyBridge.
https://www.intel.com/content/www/us/en/...pencl.html

I was not able to use hashcat on Linux so far. Every time I got an "illegal hardware instruction" error.
MACs are synthetic (not real), for educational purposes only. Details are here

v5.1.0 took about 5 seconds.

v6.2.5 took about 16 minutes.

Most of the time of those 16 minutes I see this message on the screen: Initializing backend runtime for device #1. Please be patient...

-D 1  means use CPU, works for both versions of Hashcat
-D 2  means use GPU, doesn't work in my case for both versions
v6.2.5 complains: Device #2: Not enough allocatable device memory for this attack.
v5.1.0 complains: Device #2: Intel's OpenCL runtime (GPU only) is currently broken. No devices found/left.

But it is possible to use GPU with v5.1.0 using option -D 2 --force
v5.1.0 took about 5 seconds.

info about detected OpenCL platforms/devices:

Assuming the following files are the kernels for -m0 (MD5):


There are no such "optimized" kernels for -m9400 (Office 2007). Why is that?

What is the meaning of a0, a1 and a3?

Trying to use an optimized kernel I get this message:

What does it take to add such a kernel if I were to create my own?

Hi @all,

first of all english is not my mother tongue.

In september 2019 I had a motorcyle accident with Traumatic Brain Injury (tbi), broken upper leg and impressions fracture lumbar vertebra nr. 4 (? i don't know if its the proper translation but something in my lower spin was injured) and ~1 and 1/2 months coma.

Due to the tbi i have no memories of the accident.
I lost the passwords to my encripted external hard drive created with Truecrypt and i do not know which version i had when encripting the external HDD but i know i could decrypt it with TrueCrypt 7.1a. I believe i created it with TrueCrypt 7.x in 2014-2016. I did not write the password down or saved it somewhere.
I justed pluged in the external HDD, open TrueCrypt and entered my password.
I believe i know parts of it because it used several other passwords combined to one long string. This string is at least 30 or 45 characters long.

After i was able to leave hospital and reha i tried to use TrueCrypt that was installed on my pc with the passwords i believed to be rigth, but no luck. Then i created a java program that would do the entering and checking for success automatically with a list of string (i m a developer myself), no luck. Then i heard about hashcat and read a bit in the internet then i tried my luck with hashcat, but so far i had no luck, obviously.


Encrypted external HDD info

• probably encrypted with TrueCrypt 7.x in 2014 - 2016
  
• Encryption algorithm AES-TWOFISH-SERPANT or SERPANT-TWOFISH-AES
  
• Hash Algorithm SHA-512 or RIPEMD-160
  

Hashcat

• used modes in the beginning RIPEMD-160 XTS 6211,6212,6213 and SHA-512 XTS 6221,6222, 6223
  
• latet only RIPEMD-160 XTS 6213 and SHA-512 XTS 6223
  
• e.g. hastcat.exe -a 3 -w 3 -m 6213 data_to_hack masks.file -o outputfile
  

Extracted data_to_hack(DATA)

• I extracted those DATA from my external HDD by using "rawwrite dd for windows version 0.5.".
  
• dd if=\\?\Device\HarddiskVolume10 of=blackToshiba.txt count=200
  

Tests

I do no have another HDD so i was using a 32GB usb stick, encrypted it with TrueCrypt 7.1a with both algorithm mentioned above, extracted the DATA in the same way as written above, and it worked.
But it is not a HDD, and i do not exactly know if i used TrueCrypt 7.1a for encrypting so not exactly the same.

Questions

Just to be on the save side, i need confirmation that i used the correct data for hashcat even if do not know if encryption was done with TrueCrypt 7.1a or 7.x. or even 6.x - which i doubt but m not sure.
Do i m using the proper DATA?
Is the count=200 enough or do i need more?
Did i extract the correct data that is needed for my external HDD?

If i do not, can you point me to the correct way, please?


Yours
Anthony