10-09-2025, 05:49 PM
Firstly, you're using ?h which is hexadecimal, so it would search for abcdef0123456789, not full bytes, which would be ?b
Secondly, 16x?h itself is absolutely gigantic, it's 18.4 quadrillion / ~18,446,744,000,000,000,000 possible candidates, which isn't even close to the actual size of what you want to do, which is 16 bytes with ?b. In that case, it'd be 340,282,366,920,938,463,463,374,607,431,768,211,456 possible candidates, both of which are entirely unsearchable, especially by a 2080 Super.
AES-128 remains mostly secure and the only way to crack the keys without any other information is to know a large portion of it
Secondly, 16x?h itself is absolutely gigantic, it's 18.4 quadrillion / ~18,446,744,000,000,000,000 possible candidates, which isn't even close to the actual size of what you want to do, which is 16 bytes with ?b. In that case, it'd be 340,282,366,920,938,463,463,374,607,431,768,211,456 possible candidates, both of which are entirely unsearchable, especially by a 2080 Super.
AES-128 remains mostly secure and the only way to crack the keys without any other information is to know a large portion of it