您最多能選擇 25 個主題 主題必須以字母或數字為開頭,可包含連接號「-」且最長為 35 個字元。
 
 
 
 
 
移至檔案
Jens Steube fafb277e07
Merge pull request #3950 from fse-a/scrypt-performance-improvements
1 個月前
.github Use lowercase artifacts names 2 年前
OpenCL Improve performance of scrypt-based algorithms by code reordering. 1 個月前
charsets Added full charset for romanian language 8 個月前
deps Update gzlog.c 8 個月前
docs Fix changes.txt ordering 7 個月前
extra/tab_completion Add --dynamic-x parameter to bash completion script 5 個月前
include Increased-virtual-backend-limit 2 個月前
layouts Create da.hckmap 9 個月前
masks add hashcat's default mask for external use 4 年前
modules Move module sources to src/modules 5 年前
obj add missing lock file 5 年前
rules Optimized old "dive.rule" with ruleprocessorY 6 個月前
src Increased-virtual-backend-limit 2 個月前
tools Fix some file modes 6 個月前
tunings typo fix 4 個月前
.appveyor.yml.old Test disable Appveyor 1 年前
.editorconfig Fix .editorconfig suggested in #3675 12 個月前
.gitattributes Prevent the git autocrlf option from messing files 6 個月前
.gitignore Add missing entry to .gitignore for new *.debugfile 2 年前
.travis.yml add missing OpenCL path 5 年前
BUILD.md Support building windows binaries on macOS using MinGW, updated documentation 10 個月前
BUILD_CYGWIN.md Update tested windows version and add missing package 3 年前
BUILD_MSYS2.md Update tested windows version 3 年前
BUILD_WSL.md Add note about tested WSL2 configuration 3 年前
BUILD_macOS.md Support building windows binaries on macOS using MinGW, updated documentation 10 個月前
Makefile Initial commit 8 年前
README.md Remove Appveyor status from README.md 1 年前
example.dict Removed duplicated words in example.dict 6 年前
example0.cmd Fix CRLF for windows scripts 6 個月前
example0.hash Prepare to rename project into hashcat 8 年前
example0.sh fix example0*, skip autodetect if keyspace enabled, update help and changes.txt 3 年前
example400.cmd Fix CRLF for windows scripts 6 個月前
example400.hash Prepare to rename project into hashcat 8 年前
example400.sh Fix sed call in Makefile 8 年前
example500.cmd Fix CRLF for windows scripts 6 個月前
example500.hash Prepare to rename project into hashcat 8 年前
example500.sh Fix sed call in Makefile 8 年前
hashcat.hcstat2 LZMA compress version of hashcat.hcstat2 7 年前

README.md

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!