1
0
mirror of https://github.com/hashcat/hashcat.git synced 2024-11-02 05:30:19 +00:00
Go to file
2018-11-25 13:31:37 +01:00
charsets
deps Replace gitmodules with files and add support for system-wide libraries 2018-11-08 12:52:06 +01:00
docs Add Kuznyechik support for VeraCrypt kernels 2018-11-22 16:07:45 +01:00
extra/tab_completion OpenCL Runtime: Use our own yielding technique for synchronizing rather than vendor specific 2018-11-20 12:32:24 +01:00
include Support multi-byte characters for TC/VC keyboard layout mapping tables 2018-11-25 13:31:37 +01:00
layouts - Keymaps: Added hashcat keyboard mapping us.hckmap (can be used as template) 2018-11-15 22:29:03 +01:00
masks
obj Move LZMA SDK files into separate folder for compiling 2018-07-23 13:36:23 +02:00
OpenCL Support multi-byte characters for TC/VC keyboard layout mapping tables 2018-11-25 13:31:37 +01:00
rules Add "passhthrough" versions of hybrid rules (using ":") 2018-09-02 06:03:27 -08:00
src Support multi-byte characters for TC/VC keyboard layout mapping tables 2018-11-25 13:31:37 +01:00
tools Add Kuznyechik support for VeraCrypt kernels 2018-11-22 16:07:45 +01:00
.appveyor.yml switch appveyor to cygwin over https 2018-04-23 17:02:44 -07:00
.editorconfig
.gitattributes fallback for Makefile version if its not a git checkout (tarball) (refix) 2016-05-19 14:03:58 +02:00
.gitignore Fix .gitignore 2018-07-24 12:06:58 +02:00
.travis.yml remove trusty matrix expansion 2017-10-04 16:05:01 -07:00
BUILD.md Replace gitmodules with files and add support for system-wide libraries 2018-11-08 12:52:06 +01:00
example0.cmd
example0.hash
example0.sh
example400.cmd
example400.hash
example400.sh
example500.cmd
example500.hash
example500.sh
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 Update hashcat.hctune: Optimize default sm52 or higher configuration to match GTX1080 2018-10-21 10:58:09 +02:00
Makefile
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!