World's fastest and most advanced password recovery utility
C Other
Latest commit 8879039 Jan 16, 2017 @jsteube jsteube committed on GitHub Merge pull request #966 from philsmd/master
cosmetic: typo in README.md
Permalink
Failed to load latest commit information.
OpenCL Workaround added for AMDGPU-Pro OpenCL runtime: AES encrypt and decry… Jan 11, 2017
charsets Added DES_full.charset Aug 31, 2016
deps/OpenCL-Headers Moved OpenCL requirement from v1.1 to v1.2 Nov 13, 2016
docs -m 11600 = 7-Zip: added support for parsing $7z$1... and $7z$2... hashes Jan 12, 2017
extra/tab_completion Prepare for v3.30 release Jan 2, 2017
include Returncode: Added dedicated returncode (see docs/status_codes.txt) fo… Jan 6, 2017
masks Prepare to rename project into hashcat May 10, 2016
obj Initial commit Dec 4, 2015
rules Removed duplicate rule 'cl' & 'l' Jun 19, 2016
src -m 11600 = 7-Zip: added support for parsing $7z$1... and $7z$2... hashes Jan 12, 2017
tools Update tc_tests/hashcat_ripemd160_aes_boot.tc for reference Jan 5, 2017
.editorconfig Add an .editorconfig file enforcing some of the code style. See Dec 10, 2015
.gitattributes fallback for Makefile version if its not a git checkout (tarball) (re… May 19, 2016
.gitignore This commit splits the native hashcat binary into the hashcat library… Dec 29, 2016
.gitmodules Using git submodule add Sep 2, 2016
.travis.yml Fix .travis.yml to use submodule Sep 2, 2016
BUILD.md Added docs/credits.txt Sep 11, 2016
Makefile Initial commit Dec 4, 2015
README.md cosmetic: typo in README.md Jan 13, 2017
example.dict Prepare to rename project into hashcat May 10, 2016
example0.cmd Prepare to rename project into hashcat May 10, 2016
example0.hash Prepare to rename project into hashcat May 10, 2016
example0.sh Fix sed call in Makefile Jun 11, 2016
example400.cmd Prepare to rename project into hashcat May 10, 2016
example400.hash Prepare to rename project into hashcat May 10, 2016
example400.sh Fix sed call in Makefile Jun 11, 2016
example500.cmd Prepare to rename project into hashcat May 10, 2016
example500.hash Prepare to rename project into hashcat May 10, 2016
example500.sh Fix sed call in Makefile Jun 11, 2016
hashcat.hcstat Improved default hashcat.hcstat Nov 11, 2016
hashcat.hctune Creating aliases for Apple GPU types in hctune Jan 11, 2017

README.md

hashcat

hashcat is the world's fastest and most advanced password recovery utility, supporting five unique modes of attack for over 160 highly-optimized hashing algorithms. hashcat currently supports CPU's, GPU's and other hardware-accelerators on Linux, Windows and OSX, 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 Forums also contain a plethora of information.

Building

Hashcat Build status

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

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 public domain (BSD, GPL, etc. code is incompatible)
  2. Adheres to either C89, C90, or C99 standards
  3. Compiles cleanly with no warnings when compiled with -W -Wall -std=c99
  4. Uses Allman-style code blocks & indentation
  5. Uses 2-spaces as 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 optimizes 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!