1
0
mirror of https://github.com/hashcat/hashcat.git synced 2025-07-08 07:38:17 +00:00
Go to file
Jens Steube e8cf8bd146 Fix OpenCL spawning unnecessary work-item due to redundant multiplication in new OPTS_TYPE_THREAD_MULTI_DISABLE mode.
Prepare Metal section in run_kernel() for 2D kernel invocation related to new salt->salt_dimy variable.
Move reusable Argon2 module code into separate file argon2_commit.c, similar to scrypt_commit.c, and update headers.
Update existing hash mode 34000 to use argon2_commit.c.
2025-07-03 08:10:30 +02:00
.github The Assimilation Bridge (Python plugins -m 72000 and -m 73000) 2025-06-02 10:15:34 +02:00
bridges The Assimilation Bridge (Framework) 2025-05-29 15:38:13 +02:00
charsets
deps - Replace naive 32 bit rotate with funnelshift on CUDA/HIP 2025-06-02 11:50:08 +02:00
docker - Add CPU SIMD detection at runtime, relevant for bridge plugins 2025-06-04 10:09:44 +02:00
docs Merge pull request #4273 from matrix/backend_ctx_devices_init_splitted 2025-07-01 20:24:43 +02:00
extra/tab_completion Added option --backend-devices-keepfree to configure X percentage of device memory available to keep free 2025-06-04 10:13:29 +02:00
include Modified the automatic kernel-accel count reduction routine to also reduce kernel-thread count if insufficient device or host memory is available. 2025-06-30 19:38:54 +02:00
layouts
masks
modules The Assimilation Bridge (Framework) 2025-05-29 15:38:13 +02:00
obj The Assimilation Bridge (Framework) 2025-05-29 15:38:13 +02:00
OpenCL porting to metal and fix OpenCL bug on hc__shfl 2025-07-02 22:19:39 +02:00
Python Switched all async and non-blocking calls to synchronous and blocking ones. Kept the original async bindings intact. This avoids race conditions like the one fixed in the previous commit, with no performance impact. 2025-06-30 11:26:05 +02:00
rules
src Fix OpenCL spawning unnecessary work-item due to redundant multiplication in new OPTS_TYPE_THREAD_MULTI_DISABLE mode. 2025-07-03 08:10:30 +02:00
tools Add Argon2 support for OpenCL and HIP 2025-07-02 11:02:57 +02:00
tunings Improvements to SCRYPT autotuning strategy 2025-06-09 11:02:34 +02:00
.appveyor.yml.old
.editorconfig
.gitattributes
.gitignore add .so/.dll from bridges directory in .gitignore 2025-06-07 22:52:11 +02:00
.travis.yml
BUILD_CYGWIN.md update BUILD_CYGWIN: add python3.12 to dependencies 2025-06-08 17:08:11 +02:00
BUILD_Docker.md Add build Dockerfiles for binary compilation. 2025-05-30 07:37:19 +02:00
BUILD_macOS.md - Remove old iconv patches (replaced by cmake) 2025-06-05 06:56:38 +02:00
BUILD_MSYS2.md update BUILD_MSYS2: add python3 to dependencies 2025-06-08 14:10:22 +02:00
BUILD_WSL.md - Remove old iconv patches (replaced by cmake) 2025-06-05 06:56:38 +02:00
BUILD.md Update BUILD.md 2025-06-07 13:21:31 +02:00
example0.cmd
example0.hash
example0.sh
example400.cmd
example400.hash
example400.sh
example500.cmd
example500.hash
example500.sh
example.dict
hashcat.hcstat2
Makefile
README.md

hashcat

hashcat is the world's fastest and most advanced password recovery utility, supporting five unique modes of attack for over 300 highly-optimized hashing algorithms. hashcat currently supports CPUs, GPUs, and other hardware accelerators on Linux, Windows, and macOS, and has facilities to help enable distributed password cracking.

License

hashcat is licensed under the MIT license. Refer to docs/license.txt for more information.

Installation

Download the latest release and unpack it in the desired location. Please remember to use 7z x when unpacking the archive from the command line to ensure full file paths remain intact.

Usage/Help

Please refer to the Hashcat Wiki and the output of --help for usage information and general help. A list of frequently asked questions may also be found here. The Hashcat Forum also contains a plethora of information. If you still think you need help by a real human come to Discord.

Building

Refer to BUILD.md for instructions on how to build hashcat from source.

Tests:

Travis Coverity GitHub Actions
Hashcat Travis Build status Coverity Scan Build Status Hashcat GitHub Actions Build status

Contributing

Contributions are welcome and encouraged, provided your code is of sufficient quality. Before submitting a pull request, please ensure your code adheres to the following requirements:

  1. Licensed under MIT license, or dedicated to the public domain (BSD, GPL, etc. code is incompatible)
  2. Adheres to gnu99 standard
  3. Compiles cleanly with no warnings when compiled with -W -Wall -std=gnu99
  4. Uses Allman-style code blocks & indentation
  5. Uses 2-spaces as the indentation or a tab if it's required (for example: Makefiles)
  6. Uses lower-case function and variable names
  7. Avoids the use of ! and uses positive conditionals wherever possible (e.g., if (foo == 0) instead of if (!foo), and if (foo) instead of if (foo != 0))
  8. Use code like array[index + 0] if you also need to do array[index + 1], to keep it aligned

You can use GNU Indent to help assist you with the style requirements:

indent -st -bad -bap -sc -bl -bli0 -ncdw -nce -cli0 -cbi0 -pcs -cs -npsl -bs -nbc -bls -blf -lp -i2 -ts2 -nut -l1024 -nbbo -fca -lc1024 -fc1

Your pull request should fully describe the functionality you are adding/removing or the problem you are solving. Regardless of whether your patch modifies one line or one thousand lines, you must describe what has prompted and/or motivated the change.

Solve only one problem in each pull request. If you're fixing a bug and adding a new feature, you need to make two separate pull requests. If you're fixing three bugs, you need to make three separate pull requests. If you're adding four new features, you need to make four separate pull requests. So on, and so forth.

If your patch fixes a bug, please be sure there is an issue open for the bug before submitting a pull request. If your patch aims to improve performance or optimize an algorithm, be sure to quantify your optimizations and document the trade-offs, and back up your claims with benchmarks and metrics.

In order to maintain the quality and integrity of the hashcat source tree, all pull requests must be reviewed and signed off by at least two board members before being merged. The project lead has the ultimate authority in deciding whether to accept or reject a pull request. Do not be discouraged if your pull request is rejected!

Happy Cracking!