AES-128 and Integer overflow detected in keyspace of mask
#5
(10-09-2025, 06:26 PM)penguinkeeper Wrote: In your example, you have 32 hexadecimal characters, which makes your mask half the size it should be, which blows it up into the same 3.4e38, which also makes it unsearchable. Even if you have the first 2 bytes, it doesn't matter and is still far, far, far from searchable but you can just replace the "?h"es with your known character, like "b3?h?h?h..."

Feasibility - yes, not possible, but as I said, I try to get the correct command syntax

Mask - not sure if your mask is correct. I'm looking for hex code.
Assuming I know the first (0x00) and the last byte (0xFF).
1. "00?h?hff" -> "Candidates.#01...: 00acff -> 00f7ff"
2. "00?b?bff" -> "Candidates.#01...: 00niff -> $HEX[3030ffff6666]"

1. is your mask. I believe this is text in hex code, but I need hex.
2. with "?b", it's wrong as well.

Adding the argument "--hex-charset" does the job (I believe).
3. "00?b?bff" -> "Candidates.#01...: $HEX[006172ff] -> $HEX[00ffffff]"

I don't know why the candidate doesn't start with 0x000000ff, but the mask looks fine this time.
Reply


Messages In This Thread
RE: AES-128 and Integer overflow detected in keyspace of mask - by strcmp - 10-10-2025, 05:20 AM