1
0
mirror of https://github.com/hashcat/hashcat.git synced 2024-11-15 20:39:17 +00:00
Go to file
2019-05-14 15:43:01 +02:00
charsets Order some of the new DES charset files 2017-07-04 09:50:07 +02:00
deps add the zlib 1.2.11 source code to the dependencies 2019-05-07 15:18:49 +02:00
docs Merge remote-tracking branch 'upstream/master' 2019-05-14 11:48:44 +02:00
extra/tab_completion Rename some more variables 2019-05-01 15:52:56 +02:00
include Show host memory requirement on startup 2019-05-10 16:37:49 +02:00
layouts User contribution: swiss keyboard layout (french) 2019-01-21 15:28:04 +01:00
masks Prepare to rename project into hashcat 2016-05-10 19:07:07 +02:00
modules Move module sources to src/modules 2019-01-13 15:28:42 +01:00
obj Move LZMA SDK files into separate folder for compiling 2018-07-23 13:36:23 +02:00
OpenCL added missing pre-load 2019-05-14 15:43:01 +02:00
rules Add "passhthrough" versions of hybrid rules (using ":") 2018-09-02 06:03:27 -08:00
src all pkzip modules use u32 to store the hash data and use appropriate printing 2019-05-14 14:08:11 +02:00
tools Fix test.sh and bitsliced algos 2019-05-06 15:06:02 +02:00
.appveyor.yml Testrun with mingw and cygwin 2019-01-20 18:35:55 +01: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 Fix some unused variable warnings 2019-04-03 21:53:34 +02:00
.travis.yml remove trusty matrix expansion 2017-10-04 16:05:01 -07:00
BUILD_CYGWIN.md Link BUILD_CYGWIN.md in BUILD.md 2019-03-29 19:23:41 +01:00
BUILD_MSYS2.md Update BUILD_MSYS2.md 2019-03-29 16:39:41 +00:00
BUILD.md Link BUILD_CYGWIN.md in BUILD.md 2019-03-29 19:23:41 +01:00
example0.cmd Binary Distribution: Removed 32 bit binary executeables 2019-02-22 21:36:02 +01: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 Binary Distribution: Removed 32 bit binary executeables 2019-02-22 21:36:02 +01:00
example400.hash Prepare to rename project into hashcat 2016-05-10 19:07:07 +02:00
example400.sh Fix sed call in Makefile 2016-06-11 11:39:49 +02:00
example500.cmd Binary Distribution: Removed 32 bit binary executeables 2019-02-22 21:36:02 +01:00
example500.hash Prepare to rename project into hashcat 2016-05-10 19:07:07 +02:00
example500.sh Fix sed call in Makefile 2016-06-11 11:39:49 +02:00
example.dict Removed duplicated words in example.dict 2018-08-20 11:58:21 +02:00
hashcat.hcstat2 LZMA compress version of hashcat.hcstat2 2017-06-23 14:37:45 +02:00
hashcat.hctune Fix hashcat.hctune entry for Tegra X1 2019-05-14 10:59:33 +02:00
Makefile Initial commit 2015-12-04 15:47:52 +01:00
README.md consistent forum plural/singular (thx, unix-ninja); also, README trailing whitespace 2018-11-01 11:11:33 -08:00

hashcat

hashcat is the world's fastest and most advanced password recovery utility, supporting five unique modes of attack for over 200 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!