You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Jens Steube 3119525ea3 Fixed integer overflow in Recovered/Time status view column caused by division > 0 but < 1 7 hours ago
.github/ISSUE_TEMPLATE Update feature request GitHub issue template 3 weeks ago
OpenCL VeraCrypt: Increase password length support for non-boot volumes from 64 to 128. 1 day ago
charsets hcchr: rename some .charset files into .hcchr files 11 months ago
deps RAR3-p (Compressed): Fix workaround in unrar library in AES constant table generation to enable multi-threading support 3 weeks ago
docs Fixed integer overflow in Recovered/Time status view column caused by division > 0 but < 1 7 hours ago
extra/tab_completion Prepare for v6.2.2 6 days ago
include Fixed integer overflow in Recovered/Time status view column caused by division > 0 but < 1 7 hours ago
layouts User contribution: swiss keyboard layout (french) 2 years ago
masks add hashcat's default mask for external use 1 year ago
modules Move module sources to src/modules 2 years ago
obj add missing lock file 2 years ago
rules Add "passhthrough" versions of hybrid rules (using ":") 3 years ago
src Fixed integer overflow in Recovered/Time status view column caused by division > 0 but < 1 7 hours ago
tools Tests: Changed tests for VeraCrypt from -a 0 to -a 3, because password extension is not available to all shells 1 day ago
.appveyor.yml Disable MINGW test. It seems AppVeyor is no longer supporting MSYS2. Not a hashcat problem. See BUILD_MSYS2.md for local test. 3 months ago
.editorconfig Add an .editorconfig file enforcing some of the code style. See 6 years ago
.gitattributes fallback for Makefile version if its not a git checkout (tarball) 5 years ago
.gitignore update repo and re-apply zip patch 2 years ago
.travis.yml add missing OpenCL path 2 years ago
BUILD.md apply suggested changes 2 weeks ago
BUILD_CYGWIN.md Update tested windows version and add missing package 1 month ago
BUILD_MSYS2.md Update tested windows version 1 month ago
BUILD_WSL.md Add note about tested WSL2 configuration 3 months ago
Makefile Initial commit 6 years ago
README.md update number of supported hash types in README 1 year ago
example.dict Removed duplicated words in example.dict 3 years ago
example0.cmd fix example0*, skip autodetect if keyspace enabled, update help and changes.txt 2 weeks ago
example0.hash Prepare to rename project into hashcat 5 years ago
example0.sh fix example0*, skip autodetect if keyspace enabled, update help and changes.txt 2 weeks ago
example400.cmd Binary Distribution: Removed 32 bit binary executeables 2 years ago
example400.hash Prepare to rename project into hashcat 5 years ago
example400.sh Prepare to rename project into hashcat 5 years ago
example500.cmd Binary Distribution: Removed 32 bit binary executeables 2 years ago
example500.hash Prepare to rename project into hashcat 5 years ago
example500.sh Prepare to rename project into hashcat 5 years ago
hashcat.hcstat2 LZMA compress version of hashcat.hcstat2 4 years ago
hashcat.hctune OpenCL Backend: Use CL_DEVICE_BOARD_NAME_AMD instead of CL_DEVICE_NAME for device name in case OpenCL runtime supports this query 3 weeks ago

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.

Building

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

Tests:

Travis Appveyor Coverity
Hashcat Travis Build status Hashcat Appveyor Build status Coverity Scan 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!