Re: Quor's cipher
ghio@temp0126.myriad.ml.org (Matt Ghio) writes:
What about this:
If (a+b)^(a0+b0) == 0, then the plaintext is the same as the ciphertext. This happens for one out of every 256 bytes. Ordinarilly this isn't a problem, but if the key is reused, and there is no IV, it can leak a byte of plaintext.
So it seems that you would need to change the key for each message, or at least use a random initialization vector.
How are you planning to detect which bytes are passed in this way ? Chosen plaintext attacks would do it, and show where (a+b)^(a0+b0) == 0. Looks like you've just doubled our progress. If the key is reused with a different message I don't think there's a weakness. An IV is a good idea, but aren't we _attacking_ this thing ? I've grabbed a few search-engine hits and not read them yet. I'll be looking for clues there. -- ############################################################## # Antonomasia ant@notatla.demon.co.uk # # See http://www.notatla.demon.co.uk/ # ##############################################################
Antonomasia <ant@notatla.demon.co.uk> wrote:
How are you planning to detect which bytes are passed in this way ? Chosen plaintext attacks would do it, and show where (a+b)^(a0+b0) == 0. Looks like you've just doubled our progress.
It doesn't take chosen plaintext, just known plaintext.
If the key is reused with a different message I don't think there's a weakness. An IV is a good idea, but aren't we _attacking_ this thing ?
Lack of an IV is a problem with almost any cipher, but it seems especially so here.
Matthew Ghio wrote:
Antonomasia <ant@notatla.demon.co.uk> wrote:
How are you planning to detect which bytes are passed in this way ? Chosen plaintext attacks would do it, and show where (a+b)^(a0+b0) == 0. Looks like you've just doubled our progress.
It doesn't take chosen plaintext, just known plaintext.
Even in the case where this doesn't work, you can simply collect all 128 plaintext/ciphertext pairs for the first byte (if you can get enough known plaintexts)
participants (3)
-
Antonomasia
-
ghio@temp0130.myriad.ml.org
-
nobody@REPLAY.COM