hashcat Forum
3DES Is there a problem? where did I go wrong ? - Printable Version

+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Support (https://hashcat.net/forum/forum-3.html)
+--- Forum: hashcat (https://hashcat.net/forum/forum-45.html)
+--- Thread: 3DES Is there a problem? where did I go wrong ? (/thread-7900.html)

Pages: 1 2


3DES Is there a problem? where did I go wrong ? - kadabra117 - 10-27-2018

Hi all !

I'm use:
hashcat64 -m 14100 A8AC874BC6632F6F:bbbbbbbbbbbbbbbb -a 3 --hex-charset ?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1 -1 charsets/DES_full.charset

i'm get:
hashcat (v4.2.1-47-g6e1aec0) starting...
* Device #9: Not a native Intel OpenCL runtime. Expect massive speed loss.
             You can use --force to override, but do not report related errors.
OpenCL Platform #1: Intel(R) Corporation
========================================
* Device #1: Intel(R) Celeron(R) CPU G3930 @ 2.90GHz, skipped.
OpenCL Platform #2: Advanced Micro Devices, Inc.
================================================
* Device #2: Ellesmere, 3840/4096 MB allocatable, 36MCU
* Device #3: Ellesmere, 4048/8192 MB allocatable, 36MCU
* Device #4: Ellesmere, 3840/4096 MB allocatable, 36MCU
* Device #5: Ellesmere, 3840/4096 MB allocatable, 36MCU
* Device #6: Ellesmere, 3840/4096 MB allocatable, 36MCU
* Device #7: Ellesmere, 3840/4096 MB allocatable, 36MCU
* Device #8: Ellesmere, 3840/4096 MB allocatable, 36MCU
* Device #9: Intel(R) Celeron(R) CPU G3930 @ 2.90GHz, skipped.
Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Applicable optimizers:
* Zero-Byte
* Precompute-Final-Permutation
* Not-Iterated
* Single-Hash
* Single-Salt
* Brute-Force
Minimum password length supported by kernel: 24
Maximum password length supported by kernel: 24
Watchdog: Temperature abort trigger set to 90c
Integer overflow detected in keyspace of mask: ?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1
Started: Sat Oct 27 11:03:27 2018
Stopped: Sat Oct 27 11:03:51 2018


RE: 3DES Is there a problem? where did I go wrong ? - kadabra117 - 10-27-2018

I have only 4GB of RAM
maybe that is the problem?


RE: 3DES Is there a problem? where did I go wrong ? - philsmd - 10-27-2018

the keyspace is wayyyyyyyyy too huge.

The number of characters within the file charsets/DES_full.charset is 128

128 * 128 * 128 * 128 * ... * 128 (24 times) = 128 ^ 24 = 374144419156711147060143317175368453031918731001856

are you aware how huge this keyspace is ? it's infeasible to brute-force this without any further limitation/restriction (like all 3 of the 3 8-byte subparts are identical etc)


RE: 3DES Is there a problem? where did I go wrong ? - kadabra117 - 10-27-2018

(10-27-2018, 11:38 AM)philsmd Wrote: the keyspace is wayyyyyyyyy too huge.

The number of characters within the file charsets/DES_full.charset is 128

128 * 128 * 128 * 128 * ... * 128 (24 times) = 128 ^ 24 = 374144419156711147060143317175368453031918731001856

are you aware how huge this keyspace is ? it's infeasible to brute-force this without any further limitation/restriction (like all 3 of the 3 8-byte subparts are identical etc)

I understand that this is a very large volume
the question is, why doesn't it start ?
why the error ?


RE: 3DES Is there a problem? where did I go wrong ? - philsmd - 10-27-2018

Quote:Integer overflow

the numbers are too huge and hashcat detects this and prevents you from running such an insane keyspace. It needs special code to deal with such large numbers; and different data types to represent such large integer numbers, unsigned 128 bit numbers are not large enough, therefore there is the problem of integer overflow. Your keyspace for instance is about 170 bits.


RE: 3DES Is there a problem? where did I go wrong ? - kadabra117 - 10-27-2018

(10-27-2018, 12:19 PM)philsmd Wrote:
Quote:Integer overflow

the numbers are too huge and hashcat detects this and prevents you from running such an insane keyspace. It needs special code to deal with such large numbers; and different data types to represent such large integer numbers, unsigned 128 bit numbers are not large enough, therefore there is the problem of integer overflow. Your keyspace for instance is about 170 bits.

then another question is how to run a brute force with a certain range of keys ?


RE: 3DES Is there a problem? where did I go wrong ? - kadabra117 - 10-27-2018

for example from
AAAAAAAAAAAAAAAAAAAAAAAA
to
CCCCCCCCCCCCCCCCCCCCCCCC
?


RE: 3DES Is there a problem? where did I go wrong ? - undeath - 10-27-2018

use a smaller charset than charsets/DES_full.charset

but anyway, if you want to crack a full 3DES key there are better attacks than a full bruteforce. Just hashcat is not your tool to do them.


RE: 3DES Is there a problem? where did I go wrong ? - kadabra117 - 10-27-2018

(10-27-2018, 12:31 PM)undeath Wrote: use a smaller charset than charsets/DES_full.charset

but -1 charsets/DES_special/DES_alpha.charset
get same result Sad


RE: 3DES Is there a problem? where did I go wrong ? - kadabra117 - 10-29-2018

someone can run 3des bruteforce ?