1
0
mirror of https://github.com/hashcat/hashcat.git synced 2024-12-24 15:38:11 +00:00
Go to file
jsteube a720195686 Increase AIX {ssha512} cracking performance
Remove unrolling for 7100, 7200, 12100 and 8200: High-End GPUs didn't like it
2016-05-28 12:30:39 +02:00
charsets Initial commit 2015-12-04 15:47:52 +01:00
docs Change --status-automate to --machine-readble. The former didn't really illustrate the point of the command though the functionallity is great to have. Updated ASCII tables around options output. 2016-05-27 03:50:52 -05:00
extra/tab_completion Add --machine-readable to tab_completion 2016-05-27 21:02:42 +02:00
include Update macros to match option --machine-readable 2016-05-27 04:26:39 -05:00
masks Prepare to rename project into hashcat 2016-05-10 19:07:07 +02:00
obj Initial commit 2015-12-04 15:47:52 +01:00
OpenCL Increase AIX {ssha512} cracking performance 2016-05-28 12:30:39 +02:00
rules Prepare to rename project into hashcat 2016-05-10 19:07:07 +02:00
src Update macros to match option --machine-readable 2016-05-27 04:26:39 -05:00
tools Fix includes for kernel2cpu_rule_test 2016-05-26 12:21:08 +02:00
.editorconfig Add an .editorconfig file enforcing some of the code style. See 2015-12-10 17:11:36 +01:00
.gitattributes fallback for Makefile version if its not a git checkout (tarball) (refix) 2016-05-19 14:03:58 +02:00
.gitignore Prepare to rename project into hashcat 2016-05-10 19:07:07 +02:00
.travis.yml Add clang to .travis.yml 2016-05-26 12:07:25 +02:00
BUILD.md Moved BUILD.md to root folder 2016-05-10 19:16:57 +02:00
example0.cmd Prepare to rename project into hashcat 2016-05-10 19:07:07 +02:00
example0.hash Prepare to rename project into hashcat 2016-05-10 19:07:07 +02:00
example0.sh Prepare to rename project into hashcat 2016-05-10 19:07:07 +02:00
example400.cmd Prepare to rename project into hashcat 2016-05-10 19:07:07 +02:00
example400.hash Prepare to rename project into hashcat 2016-05-10 19:07:07 +02:00
example400.sh Prepare to rename project into hashcat 2016-05-10 19:07:07 +02:00
example500.cmd Prepare to rename project into hashcat 2016-05-10 19:07:07 +02:00
example500.hash Prepare to rename project into hashcat 2016-05-10 19:07:07 +02:00
example500.sh Prepare to rename project into hashcat 2016-05-10 19:07:07 +02:00
example.dict Prepare to rename project into hashcat 2016-05-10 19:07:07 +02:00
hashcat.hcstat Initial commit 2015-12-04 15:47:52 +01:00
hashcat.hctune Fix "abort trap: 6" for -m 6231 on OSX 2016-05-17 10:31:56 +02:00
Makefile Initial commit 2015-12-04 15:47:52 +01:00
README.md Added Travis building, placed build status in readme 2016-05-14 21:22:48 +02:00

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 other hardware-accelerators on Linux, Windows and OSX, and has facilities to help enable distributed password cracking.

** THE VERSION 3.00 IS CURRENTLY STILL IN BETA **

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!