arno/hashcat
1
0
Fork 0
mirror of https://github.com/hashcat/hashcat.git synced 2024-11-13 19:28:56 +00:00
Code Issues Releases Wiki Activity
832 Commits 1 Branch 27 Tags 191 MiB
C 91.1%
Common Lisp 5.4%
Perl 2.6%
Shell 0.4%
Python 0.3%
Other 0.1%
30933f1835
Go to file
jfoug 30933f1835 T0XlCv1.rule duplicates removed. no-op ^ and [ or $ and ]
2016-04-23 11:43:35 -05:00
charsets
docs Added parameter --potfile-path to override default potfile path 2016-04-17 19:14:55 +02:00
extra/tab_completion Add --potfile-path to tabl_completion 2016-04-18 10:01:31 +02:00
include Test fix for broken AMD support after https://github.com/hashcat/oclHashcat/pull/303 2016-04-20 21:19:15 +02:00
masks
obj
OpenCL Fix -m 5000 performance on NV after change to new standard 2016-04-21 09:01:31 +02:00
rules T0XlCv1.rule duplicates removed. no-op ^ and [ or $ and ] 2016-04-23 11:43:35 -05:00
src Accept \r as newline in thread_keypress() 2016-04-19 13:11:28 +02:00
tools Added new hash mode -m 125 = ArubaOS 2016-04-10 00:58:28 +02:00
.editorconfig Add an .editorconfig file enforcing some of the code style. See 2015-12-10 17:11:36 +01:00
.gitignore Added support for build without ADL/NVML/NVAPI (issue #120) 2016-01-20 20:55:09 +01:00
example0.cmd More cleanup 2015-12-15 13:23:32 +01:00
example0.hash
example0.sh the example*.sh files should now also use the native binary, only when we use the packaging we need to use .bin 2016-01-03 18:34:38 +01:00
example400.cmd More cleanup 2015-12-15 13:23:32 +01:00
example400.hash
example400.sh the example*.sh files should now also use the native binary, only when we use the packaging we need to use .bin 2016-01-03 18:34:38 +01:00
example500.cmd More cleanup 2015-12-15 13:23:32 +01:00
example500.hash
example500.sh the example*.sh files should now also use the native binary, only when we use the packaging we need to use .bin 2016-01-03 18:34:38 +01:00
example.dict
hashcat_tuning.hctab Add another example of an old budget GPU that benefits from higher vector width than returned by preferred 2016-02-23 20:53:55 +01:00
hashcat.hcstat
Makefile
README.md Update README.md 2015-12-06 16:42:19 +01:00

README.md

oclHashcat

oclHashcat is the world's fastest and most advanced GPGPU-based password recovery utility, supporting five unique modes of attack for over 170 highly-optimized hashing algorithms. oclHashcat currently supports AMD (OpenCL) and Nvidia (CUDA) graphics processors on GNU/Linux and Windows 7/8/10, and has facilities to help enable distributed password cracking.

License

oclHashcat 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 docs/BUILD.md for instructions on how to build oclHashcat from source.

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 either C89, C90, or C99 standards
  3. Compiles cleanly with no warnings when compiled with -W -Wall -std=c99
  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 oclHashcat 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!