3 ms·
But that’s still 25% of the original security... I get that it’s meaningless - 4x effectively 0 is still effectively 0 - but denying the math doesn’t really he
by kgermino 8y ago
But that’s still 25% of the original security...
I get that it’s meaningless - 4x effectively 0 is still effectively 0 - but denying the math doesn’t really help anything.
- zeroimpl 8y agoThe “security” of an algorithm is not defined as the duration of time required by a computer to brute force it. Much more important is how safe it is against other known or anticipated attacks.
- bcaa7f3a8bbc 8y agoI agree. The problem here is my choice of an ambiguous word, "security". Formally speaking, the "security level" or "security claim" of a cipher is defined by the computational complexity (time/memory) of breaking it, often represented as the number of bits. so the Biclique attack indeed reduced the "security" of AES to 25% of its original claim. "Security" in a broader sense can be roughly understood as "how well a system is practically protected, under a specific threat model", in this case, the underlying details, such as this minor reduction to a cipher's security claim hardly matters. I should have edited my comment to use a better word, but now it already became permanent.