1
mirror of https://github.com/hashcat/hashcat synced 2024-12-05 11:15:21 +01:00
Go to file
2021-05-22 11:14:51 +02:00
.github/ISSUE_TEMPLATE Initial new algorithm issue template 2021-05-19 09:25:47 +02:00
charsets hcchr: rename some .charset files into .hcchr files 2020-07-26 18:07:27 +02:00
deps Dependencies: Updated xxHash from 0.1.0 to v0.8.0 - Stable XXH3 2021-05-16 09:51:17 +02:00
docs UTF8-to-UTF16: Replaced naive UTF8 to UTF16 conversion with true conversion for RAR3, AES Crypt, MultiBit HD (scrypt) and Umbraco HMAC-SHA1 2021-05-22 11:14:51 +02:00
extra/tab_completion hashcat 6.2.1 2021-05-15 14:07:58 +02:00
include Kernels: Add standalone true UTF8 to UTF16 converter kernel that runs after amplifier. Use OPTS_TYPE_POST_AMP_UTF16LE from plugin 2021-05-20 14:34:24 +02:00
layouts User contribution: swiss keyboard layout (french) 2019-01-21 15:28:04 +01:00
masks add hashcat's default mask for external use 2020-05-23 12:35:41 -08:00
modules Move module sources to src/modules 2019-01-13 15:28:42 +01:00
obj add missing lock file 2019-07-29 18:46:12 +02:00
OpenCL UTF8-to-UTF16: Replaced naive UTF8 to UTF16 conversion with true conversion for RAR3, AES Crypt, MultiBit HD (scrypt) and Umbraco HMAC-SHA1 2021-05-22 11:14:51 +02:00
rules Add "passhthrough" versions of hybrid rules (using ":") 2018-09-02 06:03:27 -08:00
src UTF8-to-UTF16: Replaced naive UTF8 to UTF16 conversion with true conversion for RAR3, AES Crypt and MultiBit HD (scrypt) 2021-05-22 10:37:51 +02:00
tools AES Crypt Plugin: Replaced naive with true UTF8 to UTF16 conversion, reduced max password length to 128 and improved performance 2021-05-21 22:12:32 +02:00
.appveyor.yml Disable MINGW test. It seems AppVeyor is no longer supporting MSYS2. Not a hashcat problem. See BUILD_MSYS2.md for local test. 2021-03-28 18:29:18 +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 update repo and re-apply zip patch 2019-07-29 18:42:50 +02:00
.travis.yml add missing OpenCL path 2019-07-01 17:29:57 +02:00
BUILD_CYGWIN.md Update tested windows version and add missing package 2021-05-07 09:53:51 +02:00
BUILD_MSYS2.md Update tested windows version 2021-05-07 09:55:48 +02:00
BUILD_WSL.md Add note about tested WSL2 configuration 2021-03-29 17:43:43 +02:00
BUILD.md added WSL build documentation 2020-05-27 21:15:36 +02: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 cryptoapi opts (1) 2021-05-06 23:24:46 +02:00
Makefile Initial commit 2015-12-04 15:47:52 +01:00
README.md update number of supported hash types in README 2020-02-18 10:40:00 +01:00

hashcat

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