hashcat-beta
This project is my attempt to make installing and using hashcat easier. Specifically, it solves the following:
No need to browse to hashcat and download
No need to download all the separate processors (see their github)
The tools are automatically in your path, no need to cd into hashcat directory
hashcat doesn’t officially support running it from a separate directory. this library has it’s own fix built in to allow this.
Easy to update or fully remove
Install
$ pip install hashcat-betaRunning
Run it as if you were running hashcat normally. It exposes multiple utilities as well.
$ hashcat -h
$ pp64 -h
$ cap2hccapx -h
$ kwp -h1 maintainer
Metadata
1 maintainer
Release files for hashcat-beta 5.1.0.post4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| hashcat-beta-5.1.0.post4.tar.gz | 53.4 MB | Without provenance | Details |
Release files / hashcat-beta-5.1.0.post4.tar.gz
| Download URL | hashcat-beta-5.1.0.post4.tar.gz |
|---|---|
| Size | 53.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
86ef4c1d5cc309595f0b080a3b010f6767e0999e1c5dc9898aad5849855805e6
|
|
BLAKE2b-256 checksum How to use checksums |
adf3cde191de22f185a0eb0d783d5a954132cbe5d83a7364b9fda942c47e84a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/45.0.0 requests-toolbelt/0.9.1 tqdm/4.41.1 CPython/3.6.9
|
Security for hashcat-beta 5.1.0.post4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
