arno/hashcat
1
0
Fork 0
mirror of https://github.com/hashcat/hashcat.git synced 2024-11-05 06:58:56 +00:00
Code Issues Releases Wiki Activity
1,440 Commits 1 Branch 27 Tags 191 MiB
C 91.1%
Common Lisp 5.4%
Perl 2.6%
Shell 0.4%
Python 0.3%
Other 0.1%
ced3b3b82f
Go to file
jsteube ced3b3b82f Move global mux_counter variable into opencl_ctx_t
2016-09-20 13:26:19 +02:00
charsets Added DES_full.charset 2016-08-31 13:37:26 +02:00
deps/OpenCL-Headers Using git submodule add 2016-09-02 10:34:44 +02:00
docs Add a note in changes.txt for last change 2016-09-14 17:51:43 +02:00
extra/tab_completion Add option for show opencl info and exit 2016-09-18 15:51:47 +02:00
include Move global mux_counter variable into opencl_ctx_t 2016-09-20 13:26:19 +02:00
masks Prepare to rename project into hashcat 2016-05-10 19:07:07 +02:00
obj
OpenCL Fix missing pwlen copy in amp_a0 2016-09-16 23:56:05 +02:00
rules Removed duplicate rule 'cl' & 'l' 2016-06-19 18:59:37 +03:00
src Move global mux_counter variable into opencl_ctx_t 2016-09-20 13:26:19 +02:00
tools Added docs/credits.txt 2016-09-11 22:20:15 +02:00
.editorconfig
.gitattributes
.gitignore Add missing check for opencl_ctx_init() 2016-09-18 18:30:32 +02:00
.gitmodules Using git submodule add 2016-09-02 10:34:44 +02:00
.travis.yml Fix .travis.yml to use submodule 2016-09-02 10:41:08 +02:00
BUILD.md Added docs/credits.txt 2016-09-11 22:20:15 +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 Fix sed call in Makefile 2016-06-11 11:39:49 +02:00
example400.cmd
example400.hash
example400.sh Fix sed call in Makefile 2016-06-11 11:39:49 +02:00
example500.cmd Prepare to rename project into hashcat 2016-05-10 19:07:07 +02:00
example500.hash
example500.sh Fix sed call in Makefile 2016-06-11 11:39:49 +02:00
example.dict Prepare to rename project into hashcat 2016-05-10 19:07:07 +02:00
hashcat.hcstat
hashcat.hctune Add GTX 1070 to tuning database 2016-06-21 11:18:17 +02:00
Makefile
README.md Fix a broken url to travis build status 2016-06-30 08:51:05 +02:00

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 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!