1
0
mirror of https://github.com/hashcat/hashcat.git synced 2024-11-26 18:08:20 +00:00
Go to file
Jens Steube 907ded0b03 Merge pull request #1378 from philsmd/master
fixed problem with cached word lists (dictstat2): nanoseconds must be considered/ignored too
2017-09-29 18:14:16 +02:00
charsets Order some of the new DES charset files 2017-07-04 09:50:07 +02:00
deps/OpenCL-Headers Wordlist encoding: Support added for internal convert from and to user-defined encoding during runtime 2017-04-14 16:36:28 +02:00
docs fixed problem with cached word lists (dictstat2): nanoseconds must be considered/ignored too 2017-09-29 12:13:29 +02:00
extra/tab_completion Splitted DPAPI kernel in 2 to increase performances 2017-09-21 12:23:33 +02:00
include fixed problem with cached word lists (dictstat2): nanoseconds must be considered/ignored too 2017-09-29 12:13:29 +02:00
masks Prepare to rename project into hashcat 2016-05-10 19:07:07 +02:00
obj/lzma_sdk Vectorized 1Password, cloudkeychain and added support for long passwords 2017-07-06 14:11:33 +02:00
OpenCL no volatile required here 2017-09-21 20:08:24 +02:00
rules Removed duplicate rule 'cl' & 'l' 2016-06-19 18:59:37 +03:00
src fixed problem with cached word lists (dictstat2): nanoseconds must be considered/ignored too 2017-09-29 12:13:29 +02:00
tools test.pl ready and 0 error. Ready for PR 2017-09-21 16:55:30 +02:00
.appveyor.yml Fix AppVeyor 2017-04-27 16:24:44 -07: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 .gitignore 2017-09-20 10:22:49 +02:00
.gitmodules Using git submodule add 2016-09-02 10:34:44 +02:00
.travis.yml matrix not expanding correctly 2017-03-11 10:35:50 -08:00
BUILD.md cleanup git submodule command 2017-02-09 15:17:09 -08: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 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 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 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 Prepare to rename project into hashcat 2016-05-10 19:07:07 +02:00
hashcat.hcstat2 LZMA compress version of hashcat.hcstat2 2017-06-23 14:37:45 +02:00
hashcat.hctune Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory 2017-08-23 12:43:59 +02:00
Makefile Initial commit 2015-12-04 15:47:52 +01:00
README.md Fix README, update C standard 2017-06-10 14:50:03 +02: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 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

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