+ I don't really like how almost all of it is built using 'Const' look-up tables... Only the XOR part has any real variability, and even then, it's key schedule is reusing those look-up tables once again... (ie it really is asking to be broken, if it hasn't already..)
>>18
Yeah, look for "The code book" by simon singh, it's a bestselling paperback pocket often found in airport kiosks. It explains the uncrackable quantum crypto.
It has been proven that applying Grover's algorithm to break a symmetric (secret key) algorithm by brute force requires time equal to roughly 2n/2 invocations of the underlying cryptographic algorithm, compared with roughly 2n in the classical case,[15] meaning that symmetric key lengths are effectively halved: AES-256 would have the same security against an attack using Grover's algorithm that AES-128 has against classical brute-force search (see Key size). Quantum cryptography could potentially fulfill some of the functions of public key cryptography.