Skip to content
Advanced CPU-based password recovery utility
C Makefile C++
Branch: master
Clone or download
jsteube Merge pull request #56 from philsmd/pr-limit-skip-problem
cosmetic: there is no --skip/--limit paramter in hashcat
Latest commit 2f300e0 Jan 11, 2016
Type Name Latest commit message Commit time
Failed to load latest commit information.
charsets Initial commit Dec 4, 2015
docs issue #54: fixed memory issue with some unicode algorithms Jan 9, 2016
examples Initial commit Dec 4, 2015
include Fix issues #48 and #49 Jan 7, 2016
masks Initial commit Dec 4, 2015
obj Rewrite Makefile so that it allows easier integration of native targets Dec 12, 2015
rules Update unix-ninja's leetspeak file Jan 7, 2016
salts Initial commit Dec 4, 2015
tables Initial commit Dec 4, 2015
tools Update (prevent reinstalling .deb) and .gitignore (update obj… Dec 15, 2015
.gitignore Update (prevent reinstalling .deb) and .gitignore (update obj… Dec 15, 2015
Makefile Update Dec 6, 2015


Hashcat is an advanced CPU-based password recovery utility for Windows 7/8/10, Apple OS X, and GNU/Linux, supporting seven unique modes of attack for over 100 optimized hashing algorithms.


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


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.


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.


Refer to docs/ for instructions on how to build Hashcat from source.


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!

You can’t perform that action at this time.