Skip to content

Instantly share code, notes, and snippets.

@roycewilliams
Last active May 18, 2021 18:34
Show Gist options
  • Save roycewilliams/4aa6a6d8d4822a02dcd23f0c907e6828 to your computer and use it in GitHub Desktop.
Save roycewilliams/4aa6a6d8d4822a02dcd23f0c907e6828 to your computer and use it in GitHub Desktop.
bcrypt-example
$ cat ~/bcrypt.hash
$2a$05$LhayLxezLhK1LhWvKxCyLOj0j1u.Kj0jZ0pEmm134uzrQlFvQJLF6
$ cat ~/bcrypt.dict
hashcat
$ ./hashcat64.bin -a 0 -m 3200 ~/bcrypt.hash ~/bcrypt.dict
hashcat (v3.10-143-g7f59a82) starting...
OpenCL Platform #1: NVIDIA Corporation
======================================
- Device #1: GeForce GTX 970, 1023/4095 MB allocatable, 13MCU
- Device #1: WARNING! Kernel exec timeout is not disabled, it might cause you errors of code 702
See the wiki on how to disable it: https://hashcat.net/wiki/doku.php?id=timeout_patch
- Device #2: GeForce GTX 750 Ti, 511/2047 MB allocatable, 5MCU
- Device #2: WARNING! Kernel exec timeout is not disabled, it might cause you errors of code 702
See the wiki on how to disable it: https://hashcat.net/wiki/doku.php?id=timeout_patch
Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1
Applicable Optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 75c
- Device #1: Kernel m03200.aa229524.kernel not found in cache! Building may take a while...
- Device #1: Kernel amp_a0.aa229524.kernel not found in cache! Building may take a while...
- Device #2: Kernel m03200.aa42b592.kernel not found in cache! Building may take a while...
- Device #2: Kernel amp_a0.aa42b592.kernel not found in cache! Building may take a while...
WARNING: Failed to set initial fan speed for device #1
WARNING: Failed to set initial fan speed for device #2
Generated dictionary stats for /home/royce/bcrypt.dict: 8 bytes, 1 words, 1 keyspace
ATTENTION!
The wordlist or mask you are using is too small.
Therefore, hashcat is unable to utilize the full parallelization power of your device(s).
The cracking speed will drop.
Workaround: https://hashcat.net/wiki/doku.php?id=frequently_asked_questions#how_to_create_more_work_for_full_speed
INFO: approaching final keyspace, workload adjusted
$2a$05$LhayLxezLhK1LhWvKxCyLOj0j1u.Kj0jZ0pEmm134uzrQlFvQJLF6:hashcat
Session.Name...: hashcat
Status.........: Cracked
Input.Mode.....: File (/home/royce/bcrypt.dict)
Hash.Target....: $2a$05$LhayLxezLhK1LhWvKxCyLOj0j1u.Kj0jZ0...
Hash.Type......: bcrypt, Blowfish(OpenBSD)
Time.Started...: 0 secs
Speed.Dev.#1...: 0 H/s (6.16ms)
Speed.Dev.#2...: 0 H/s (0.00ms)
Speed.Dev.#*...: 0 H/s
Recovered......: 1/1 (100.00%) Digests, 1/1 (100.00%) Salts
Progress.......: 1/1 (100.00%)
Rejected.......: 0/1 (0.00%)
Started: Wed Sep 21 11:28:54 2016
Stopped: Wed Sep 21 11:29:04 2016
@Habibu-R-ahman
Copy link

How to set salt?

@roycewilliams
Copy link
Author

You usually don't have to - what's the use case?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment