3 ms·
A key size of 1 bit.
by Someone1234 10y ago
A key size of 1 bit.
- tptacek 10y agoNo secure algorithm is defined at that key size. There is no straightforward way to arrive at, say, 64 bit AES. Key size is not simply a dial you can turn everywhere.
- Someone1234 10y agoYou said "key size is literally irrelevant," if it is "literally irrelevant" and you weren't just being hyperbolic then 1 bit should be sufficient. You can definitely implement most algorithms to take in a 1 bit or 1 byte key, padding for one, just because it isn't widely supported doesn't change that fact. So when you say something is "literally irrelevant" and ask for counterexamples, don't be surprised when someone gives them to you. Obviously a 1 bit or 1 byte key is absurd. But so is claiming that key length is "literally irrelevant" and "does not matter."
- tptacek 10y agoNot interested in this particular semantic debate, sorry.
- deleted 10y ago[deleted]
- zeveb 10y ago> There is no straightforward way to arrive at, say, 64 bit AES. Sure there is: zero-pad to 128, 192 or 256 bits. That'd be horribly, terribly broken, but it would be 64-bit AES. Horrible, terrible 64-bit AES, but AES nonetheless.
- tptacek 10y agoI wrote "no straightforward way" in anticipation of someone coming up with some bizarre way to adapt AES to a small key size. If we all just stipulate that we understand how block ciphers work, we don't have to waste time in blind alleys like this.
- devishard 10y ago> No secure algorithm is defined at that key size. HMAC-SHA256 is.