Welcome to PyBozoCrack’s documentation!¶
Contents:
PyBozoCrack¶
PyBozoCrack is a depressingly effective MD5 password hash cracker with almost zero CPU/GPU load written in Python. Instead of rainbow tables, dictionaries, or brute force, PyBozoCrack simply finds the plaintext password. Specifically, it googles the MD5 hash and hopes the plaintext appears somewhere on the first page of results.
- Free software: BSD license
It works way better than it ever should. Go ahead and try.
How?¶
Basic usage:
$ python pybozocrack.py -f my_md5_hashes.txt
Or:
$ python pybozocrack.py -s fcf1eed8596699624167416a1e7e122e
The input file has no specified format. BozoCrack automatically picks up strings that look like MD5 hashes. A single line shouldn’t contain more than one hash.
Example with output:
$ python pybozocrack.py -f example.txt
Loaded 5 unique hashes
fcf1eed8596699624167416a1e7e122e:octopus
bed128365216c019988915ed3add75fb:passw0rd
d0763edaa9d9bd2a9516280e9044d885:monkey
dfd8c10c1b9b58c8bf102225ae3be9eb:12081977
ede6b50e7b5826fe48fc1f0fe772c48f:1q2w3e4r5t6y
$ python pybozocrack.py -s fcf1eed8596699624167416a1e7e122e
fcf1eed8596699624167416a1e7e122e:octopus
Why?¶
To show just how bad an idea it is to use plain MD5 as a password hashing mechanism. Honestly, if the passwords can be cracked with this software, there are no excuses.
Who?¶
BozoCrack was originally written by Juuso Salonen (http://twitter.com/juusosalonen).
PyBozoCrack was rewritten in Python by Henrique Pereira (http://twitter.com/ikkebr).
Installation¶
At the command line:
$ easy_install pybozocrack
Or, if you have virtualenvwrapper installed:
$ mkvirtualenv pybozocrack
$ pip install pybozocrack
Contributing¶
Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.
You can contribute in many ways:
Types of Contributions¶
Report Bugs¶
Report bugs at https://github.com/ikkebr/pybozocrack/issues.
If you are reporting a bug, please include:
- Your operating system name and version.
- Any details about your local setup that might be helpful in troubleshooting.
- Detailed steps to reproduce the bug.
Fix Bugs¶
Look through the GitHub issues for bugs. Anything tagged with “bug” is open to whoever wants to implement it.
Implement Features¶
Look through the GitHub issues for features. Anything tagged with “feature” is open to whoever wants to implement it.
Write Documentation¶
PyBozoCrack could always use more documentation, whether as part of the official PyBozoCrack docs, in docstrings, or even on the web in blog posts, articles, and such.
Submit Feedback¶
The best way to send feedback is to file an issue at https://github.com/ikkebr/pybozocrack/issues.
If you are proposing a feature:
- Explain in detail how it would work.
- Keep the scope as narrow as possible, to make it easier to implement.
- Remember that this is a volunteer-driven project, and that contributions are welcome :)
Get Started!¶
Ready to contribute? Here’s how to set up pybozocrack for local development.
Fork the pybozocrack repo on GitHub.
Clone your fork locally:
$ git clone git@github.com:your_name_here/pybozocrack.git
Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development:
$ mkvirtualenv pybozocrack $ cd pybozocrack/ $ python setup.py develop
Create a branch for local development:
$ git checkout -b name-of-your-bugfix-or-feature
Now you can make your changes locally.
When you’re done making changes, check that your changes pass flake8 and the tests, including testing other Python versions with tox:
$ flake8 pybozocrack tests $ python setup.py test $ tox
To get flake8 and tox, just pip install them into your virtualenv.
Commit your changes and push your branch to GitHub:
$ git add . $ git commit -m "Your detailed description of your changes." $ git push origin name-of-your-bugfix-or-feature
Submit a pull request through the GitHub website.
Pull Request Guidelines¶
Before you submit a pull request, check that it meets these guidelines:
- The pull request should include tests.
- If the pull request adds functionality, the docs should be updated. Put your new functionality into a function with a docstring, and add the feature to the list in README.rst.
- The pull request should work for Python 2.6, 2.7, and 3.3, and for PyPy. Check https://travis-ci.org/ikkebr/pybozocrack/pull_requests and make sure that the tests pass for all supported Python versions.
Credits¶
Development Lead¶
- Henrique Pereira <ikkibr@gmail.com>
Contributors¶
None yet. Why not be the first?