1
0
mirror of https://github.com/hashcat/hashcat.git synced 2024-11-10 09:31:08 +00:00
Go to file
2024-04-20 17:35:45 +00:00
.github Use lowercase artifacts names 2022-07-19 14:27:45 +02:00
charsets Added full charset for romanian language 2023-07-26 10:13:18 +03:00
deps Update gzlog.c 2023-08-11 11:46:19 +08:00
docs Fix changes.txt ordering 2023-08-27 14:40:24 +00:00
extra/tab_completion Add --dynamic-x parameter to bash completion script 2023-11-05 11:52:57 +00:00
include Increased-virtual-backend-limit 2024-01-25 10:27:38 +01:00
layouts Create da.hckmap 2023-06-28 11:23:39 +02: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 Add support for zero-length salts in Electrum $4 and $5 2024-04-20 17:35:45 +00:00
rules Optimized old "dive.rule" with ruleprocessorY 2023-10-12 11:07:26 +03:00
src Add support for zero-length salts in Electrum $4 and $5 2024-04-20 17:35:45 +00:00
tools Fix some file modes 2023-09-18 07:19:23 +00:00
tunings typo fix 2023-11-20 10:06:12 +02:00
.appveyor.yml.old Test disable Appveyor 2022-12-30 18:45:40 +00:00
.editorconfig Fix .editorconfig suggested in #3675 2023-04-10 17:23:29 +00:00
.gitattributes Prevent the git autocrlf option from messing files 2023-09-27 20:53:36 -07:00
.gitignore Add missing entry to .gitignore for new *.debugfile 2022-05-01 15:53:26 +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_macOS.md Support building windows binaries on macOS using MinGW, updated documentation 2023-05-28 21:21:20 +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 Support building windows binaries on macOS using MinGW, updated documentation 2023-05-28 21:21:20 +02:00
example0.cmd Fix CRLF for windows scripts 2023-09-25 16:57:01 +00:00
example0.hash Prepare to rename project into hashcat 2016-05-10 19:07:07 +02:00
example0.sh fix example0*, skip autodetect if keyspace enabled, update help and changes.txt 2021-06-06 15:48:04 +02:00
example400.cmd Fix CRLF for windows scripts 2023-09-25 16:57:01 +00: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 Fix CRLF for windows scripts 2023-09-25 16:57:01 +00: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
Makefile Initial commit 2015-12-04 15:47:52 +01:00
README.md Remove Appveyor status from README.md 2023-01-02 17:13:45 +00: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. If you still think you need help by a real human come to Discord.

Building

Refer to BUILD.md for instructions on how to build hashcat from source.

Tests:

Travis Coverity GitHub Actions
Hashcat Travis Build status Coverity Scan Build Status Hashcat GitHub Actions 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!