|
Search Results
|
| Post
[desc]
|
Author |
Forum |
Replies |
Views |
Posted |
| |
|
Thread: Seperator unmatched error
Post: RE: Seperator unmatched error
| there is obviously no salt supplied. Also your "sha1" hash is 24bytes long, not 20 like it is supposed to be. |
|
undeath |
Old hashcat Support
|
1 |
6,301 |
08-05-2012, 05:46 PM |
| |
|
Thread: Session recovery with multiple gpu's
Post: RE: Session recovery with multiple gpu's
| Session restores work checkpoint-based. hashcat will always continue from the last reached checkpoint on. If that one happens to have been a while back that's simply what it is. |
|
undeath |
hashcat
|
4 |
1,618 |
02-16-2020, 03:20 PM |
| |
|
Thread: Session recovery with multiple gpu's
Post: RE: Session recovery with multiple gpu's
| More GPUs means more parallelization means more variance between reaching checkpoints. Pressing C stops after some new checkpoint has been reached, but that still means that devices working already on... |
|
undeath |
hashcat
|
4 |
1,618 |
02-16-2020, 10:50 PM |
| |
|
Thread: Several Words + #'s + characters
Post: RE: Several Words + #'s + characters
| for the wordlist you can use princeprocessor (https://hashcat.net/wiki/doku.php?id=princeprocessor). To append the numbers+specials you can use rules. |
|
undeath |
hashcat
|
1 |
651 |
01-28-2020, 05:06 PM |
| |
|
Thread: SHA-256 Problem
Post: RE: SHA-256 Problem
| this is most likely a charset problem.
Code:
--
> Desktop/hashcat-0.46/hashcat-cli64.bin -m 1400 /tmp/a -1 testÄ "?1?1?1?1?1?1" -a3 --pw-min 6
Initializing hashcat v0.46 by atom with 8 threads... |
|
undeath |
General Help
|
6 |
14,996 |
08-11-2013, 09:03 PM |
| |
|
Thread: SHA-256 Problem
Post: RE: SHA-256 Problem
| UTF8 needs two bytes (thus two chars) to encode the special chars. |
|
undeath |
General Help
|
6 |
14,996 |
08-11-2013, 10:40 PM |
| |
|
Thread: sha1 64 hex with only 8 variables
Post: RE: sha1 64 hex with only 8 variables
| hashcat supports at most 55bytes of plaintext. |
|
undeath |
Old oclHashcat Support
|
3 |
6,145 |
06-26-2014, 12:06 PM |
| |
|
Thread: SHA1 Customized Algorithm
Post: RE: SHA1 Customized Algorithm
| save the hashes as
hash:USER:
(notice the trailing colon)
and use a rule to ensure every password is only tested in upper case.
then you can use sha1(salt.pass) |
|
undeath |
Very old oclHashcat-lite Support
|
5 |
11,207 |
08-03-2012, 01:06 PM |
| |
|
Thread: SHA1 hashes of email addresses
Post: RE: SHA1 hashes of email addresses
| oclhashcat-plus is limited to 15 chars. |
|
undeath |
Very old oclHashcat-plus Support
|
3 |
7,232 |
02-01-2013, 09:30 PM |
| |
|
Thread: SHA1 key stretching
Post: RE: SHA1 key stretching
| you could probably modify jtr. |
|
undeath |
Very old oclHashcat-lite Support
|
5 |
10,862 |
02-04-2013, 05:01 PM |
| |
|
Thread: SHA1 with long salt - alternatives?
Post: RE: SHA1 with long salt - alternatives?
| it's not the length of hash:salt that matters but salt+password length with is restricted to 55 chars. For longer combinations you can try jtr. |
|
undeath |
Old oclHashcat Support
|
5 |
9,469 |
04-13-2014, 06:19 PM |
| |
|
Thread: SHA1_HMAC for unknown text
Post: RE: SHA1_HMAC for unknown text
| What do you mean by "unknown text"? What is the technical difference to a password? |
|
undeath |
hashcat
|
9 |
5,500 |
03-16-2018, 10:59 AM |
| |
|
Thread: SHA1_HMAC for unknown text
Post: RE: SHA1_HMAC for unknown text
| isn't that just the same as hmac-sha1(key = $pass)?
edit: according to the argument order of hmac it should probably be hmac-sha1(key = $salt) |
|
undeath |
hashcat
|
9 |
5,500 |
03-16-2018, 11:19 AM |
| |
|
Thread: SHA1_HMAC for unknown text
Post: RE: SHA1_HMAC for unknown text
| you should be able to crack this by using
dfdf3c415d1513cc2664beecb8dad840b2132c28:17513529ea04fde116862d745a91afe0e7623ba6 --hex-salt -m 160 |
|
undeath |
hashcat
|
9 |
5,500 |
03-16-2018, 11:29 AM |
| |
|
Thread: SHA1_HMAC for unknown text
Post: RE: SHA1_HMAC for unknown text
| btw, here is a mask file for ipv4 addresses without leading zeros: https://pastebin.com/4HQ6C8gG |
|
undeath |
hashcat
|
9 |
5,500 |
03-16-2018, 12:23 PM |
| |
|
Thread: SHA256 bug when salt is really big?
Post: RE: SHA256 bug when salt is really big?
| see 2.3 and 2.4, looks like a bug. have not tried to reproduce. |
|
undeath |
Old oclHashcat Support
|
9 |
16,282 |
02-13-2014, 09:17 PM |
| |
|
Thread: sha512($salt.$pass)
Post: RE: sha512($salt.$pass)
|
undeath |
Feature Requests
|
10 |
30,352 |
02-27-2012, 10:17 PM |
| |
|
Thread: sha512(sha512($pass).$salt)
Post: RE: sha512(sha512($pass).$salt)
| if it's not implemented you have to implement it yourself. |
|
undeath |
hashcat
|
3 |
3,399 |
12-28-2017, 10:20 PM |
| |
|
Thread: SHA512crypt Hash Error in notepad file, not in Unix file nor quotes
Post: RE: SHA512crypt Hash Error in notepad file, not in...
| Windows notepad is awful, use Notepad++ |
|
undeath |
Very old oclHashcat-plus Support
|
2 |
7,131 |
03-24-2013, 02:36 PM |
| |
|
Thread: Signal database password on Android
Post: RE: Signal database password on Android
| Usually the hash output is used as a key for the encryption. Having the hash in the file would mean the AES key is in the file which they are very likely not doing. Hence you have to use the pbkdf2 re... |
|
undeath |
hashcat
|
2 |
2,470 |
06-09-2018, 10:36 AM |
