|
Search Results
|
| Post
[desc]
|
Author |
Forum |
Replies |
Views |
Posted |
| |
|
Thread: +55 minutes in Generating Dictionary for 194GB
Post: RE: +55 minutes in Generating Dictionary for 194GB
| by the way, it doesn't seem that ethereum uses "just sha3", see https://github.com/ethereum/cpp-ethereum/blob/develop/libdevcrypto/SecretStore.cpp#L378-L418
It seems that the SHA3 () step is just p... |
|
philsmd |
hashcat
|
26 |
24,601 |
03-19-2017, 02:30 PM |
| |
|
Thread: +55 minutes in Generating Dictionary for 194GB
Post: RE: +55 minutes in Generating Dictionary for 194GB
| @dindolo1979 Attention: I would be very careful with this small set of information you provided/got here.
As far as I understood the algorithm is much more simple/straight forward and doesn't need an... |
|
philsmd |
hashcat
|
26 |
24,601 |
04-07-2017, 02:03 PM |
| |
|
Thread: +55 minutes in Generating Dictionary for 194GB
Post: RE: +55 minutes in Generating Dictionary for 194GB
| Yeah, in this very specific situation it might be best to have a fast (standalone) password generator (a c file, perl script etc which only generates passwords according to your "rules").
According t... |
|
philsmd |
hashcat
|
26 |
24,601 |
04-08-2017, 09:32 AM |
| |
|
Thread: +55 minutes in Generating Dictionary for 194GB
Post: RE: +55 minutes in Generating Dictionary for 194GB
| @dindolo1979
This post is just to let you know that both ethereum algorithms are now available in the newest beta version of hashcat (beta 3.5.0+168 or newer, https://hashcat.net/beta/).
See htt... |
|
philsmd |
hashcat
|
26 |
24,601 |
06-05-2017, 03:34 PM |
| |
|
Thread: +55 minutes in Generating Dictionary for 194GB
Post: RE: +55 minutes in Generating Dictionary for 194GB
| Hmm, you should be a little bit more specific about which "perl script" your are speaking about.
I probably posted too many perl scripts on the hashcat forum already so it's not easy enough for me to... |
|
philsmd |
hashcat
|
26 |
24,601 |
12-17-2017, 11:27 PM |
| |
|
Thread: +55 minutes in Generating Dictionary for 194GB
Post: RE: +55 minutes in Generating Dictionary for 194GB
| update for ethereum modes supported by hashcat:
we recently also added -m 16300 = Ethereum Pre-Sale Wallet, PBKDF2-HMAC-SHA256 (https://github.com/hashcat/hashcat/pull/1476) which is currently suppor... |
|
philsmd |
hashcat
|
26 |
24,601 |
12-20-2017, 02:20 PM |
| |
|
Thread: +55 minutes in Generating Dictionary for 194GB
Post: RE: +55 minutes in Generating Dictionary for 194GB
| You basically already answered your own question by explaining the algorithm details and linking to the algorithm description.
Furthermore, this question was already recently addressed within this fo... |
|
philsmd |
hashcat
|
26 |
24,601 |
02-10-2018, 07:39 PM |
| |
|
Thread: +55 minutes in Generating Dictionary for 194GB
Post: RE: +55 minutes in Generating Dictionary for 194GB
| The algorithm doesn't allow to recover the whole seed (if it was really generated in a cryptographically secure random way) by just knowing some bytes (let's say 80) of the encrypted seed (furthermore... |
|
philsmd |
hashcat
|
26 |
24,601 |
02-11-2018, 02:24 PM |
| |
|
Thread: +55 minutes in Generating Dictionary for 194GB
Post: RE: +55 minutes in Generating Dictionary for 194GB
| Yeah, thx undeath. When re-reading my post (after posting, hehe), I also discovered that this phrasing was not very clever and I should have added that whenever you reveal the whole seed, that the pri... |
|
philsmd |
hashcat
|
26 |
24,601 |
02-11-2018, 02:49 PM |
| |
|
Thread: +55 minutes in Generating Dictionary for 194GB
Post: RE: +55 minutes in Generating Dictionary for 194GB
| Now, thinking about the padding attack... I think an alternative could work without revealing the whole encseed.
The thing is that the pre-sale algorithm uses padding (as already mentioned a couple... |
|
philsmd |
hashcat
|
26 |
24,601 |
02-11-2018, 04:01 PM |
| |
|
Thread: --increment option
Post: RE: --increment option
| yes, your hcmask file should look like this:
Code:
--
?l
?l?d
?l?l?d
?l?l?l?d
?l?l?l?l?d
?l?l?l?l?l?d
?l?l?l?l?l?l?d
?l?l?l?l?l?l?l?d
?l?l?l?l?l?l?l?l?d
--
references:
https://hashcat... |
|
philsmd |
hashcat
|
2 |
2,441 |
08-24-2018, 03:38 PM |
| |
|
Thread: --limit and --skip usage
Post: RE: --limit and --skip usage
| your examples above have 2 different masks:
you used ?l?l?l?l?l?l?l?l for the keyspace calculation and ?l?l?l?l?l?l?l? for the actual run.
You should always use the same mask!
Furthermore, yo... |
|
philsmd |
hashcat
|
2 |
2,896 |
08-25-2017, 12:24 PM |
| |
|
Thread: --opencl-device-types vs. reported Device #?
Post: RE: --opencl-device-types vs. reported Device #?
| Please don't confuse OpenCL platforms (intel OpenCl CPU driver, Intel GPU driver, nvidia OpenCL GPU driver, AMD OpenCL CPU driver, AMD OpenCL GPU drivers, pocl opencl drivers, mesa...) with oclHashcat... |
|
philsmd |
hashcat
|
4 |
17,625 |
07-17-2016, 07:42 AM |
| |
|
Thread: --remove ?
Post: RE: --remove ?
| It is all very well explained in the FAQ: --show (https://is.gd/HiV9cw)
To sum it up: --show needs to be run on the original (not modified) hash list, it must be run after the cracking was already fin... |
|
philsmd |
Old oclHashcat Support
|
5 |
7,871 |
05-28-2015, 06:38 PM |
| |
|
Thread: --remove switch with WPA
Post: RE: --remove switch with WPA
| Like with all other hash types the file (in this case the .hccap file) should be empty if and only if all "hashes" were cracked.
The size of the hash file should therefore be 0 bytes if each and ever... |
|
philsmd |
Old oclHashcat Support
|
2 |
5,738 |
09-17-2014, 03:41 PM |
| |
|
Thread: --show doesn't print duplicates when using --username
Post: RE: --show doesn't print duplicates when using --u...
| Recently, a new feature was implemented to support exactly this.
See https://github.com/hashcat/hashcat/issues/963 and test the beta at https://hashcat.net/beta/ |
|
philsmd |
hashcat
|
2 |
6,417 |
02-02-2017, 04:12 PM |
| |
|
Thread: --show doesnt work
Post: RE: --show doesnt work
| you also need to specify the hash type. How else should cudaHashcat/oclHashcat know what type of hashes it should load?
(btw: all this info is mentioned on the wiki page that epixoip linked) |
|
philsmd |
Old oclHashcat Support
|
6 |
7,722 |
03-23-2016, 02:59 PM |
| |
|
Thread: --show problem
Post: RE: --show problem
| please read the faq page:
e.g. https://hashcat.net/wiki/frequently_asked_questions#how_can_i_show_previously_cracked_passwords_and_output_them_in_a_specific_format_eg_emailpassword
(hint: you shou... |
|
philsmd |
Old oclHashcat Support
|
6 |
13,323 |
12-12-2015, 02:43 PM |
| |
|
Thread: --show problem
Post: RE: --show problem
| The wiki page I linked to has exactly the answer for you (but I will copy it here anyways):
2 steps:
1. cracking:
Code:
--
cudaHashcat64.exe -m 0 -a 0 --username --outfile D:\cracked.txt "D:\trop... |
|
philsmd |
Old oclHashcat Support
|
6 |
13,323 |
12-12-2015, 04:19 PM |
| |
|
Thread: --show takes forever to finish
Post: RE: --show takes forever to finish
| it depends mainly on the size of the hashcat.potfile and of course also to some extend on the hashes.txt file (note there can be cracks assigned to several users, especially if unsalted hashes are use... |
|
philsmd |
hashcat
|
6 |
3,802 |
08-21-2018, 10:33 PM |
