rename -m 28503/28504 from P2WSH to P2WPKH
|20 hours ago|
|.github/ISSUE_TEMPLATE||1 year ago|
|OpenCL||4 days ago|
|charsets||3 weeks ago|
|deps||1 year ago|
|docs||20 hours ago|
|extra/tab_completion||4 months ago|
|include||1 week ago|
|layouts||3 years ago|
|masks||2 years ago|
|modules||4 years ago|
|obj||3 years ago|
|rules||3 months ago|
|src||20 hours ago|
|tools||5 days ago|
|.appveyor.yml||1 year ago|
|.gitignore||2 months ago|
|.travis.yml||3 years ago|
|BUILD.md||1 year ago|
|BUILD_CYGWIN.md||1 year ago|
|BUILD_MSYS2.md||1 year ago|
|BUILD_WSL.md||1 year ago|
|README.md||11 months ago|
|example.dict||4 years ago|
|example0.cmd||1 year ago|
|example0.sh||1 year ago|
|example400.cmd||3 years ago|
|example500.cmd||3 years ago|
|hashcat.hcstat2||5 years ago|
|hashcat.hctune||5 months ago|
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.
hashcat is licensed under the MIT license. Refer to docs/license.txt for more information.
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.
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.
Refer to BUILD.md for instructions on how to build hashcat from source.
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:
- Licensed under MIT license, or dedicated to the public domain (BSD, GPL, etc. code is incompatible)
- Adheres to gnu99 standard
- Compiles cleanly with no warnings when compiled with
-W -Wall -std=gnu99
- Uses Allman-style code blocks & indentation
- Uses 2-spaces as the indentation or a tab if it's required (for example: Makefiles)
- Uses lower-case function and variable names
- 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))
- 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!