Isn't that equivalent to sender doing XOR on the plaintext, recipient doing XOR on first ciphertext, sender doing another XOR on second ciphertext to create third ciphertext, and the recipient doing XOR again to get plaintext?
That's key-reuse and breaks XOR/OTP. The middleman simply XORs the ciphertexts with each other to get the key and then decrypts the first ciphertext. He just simply needs to record all ciphertexts. The same basic method applies for the noise application/removal. Den 13 jun 2013 17:31 skrev "Leandro Meiners" <lmein...@gmail.com>: > Koenig's idea is interesting, and with a small twist I think could have > worked. If instead of only applying noise at the receiving end, noise was > first applied by the sender, then the recipient applies his own noise and > sends it back to the sender, who then subtracts his original noise and > sends it back "encrypted" with the recipient's noise who can now decrypt > it.... > > Cheers, > Leandro.- > > > On Thu, Jun 13, 2013 at 3:31 PM, John Young <j...@pipeline.com> wrote: > >> Old Mystery Solved: Project C-43 and Public Key Encryption: >> >> http://techpinions.com/an-old-**mystery-solved-project-c-43-** >> and-public-key-encryption/**18205<http://techpinions.com/an-old-mystery-solved-project-c-43-and-public-key-encryption/18205> >> >> >> ______________________________**_________________ >> cryptography mailing list >> cryptography@randombit.net >> http://lists.randombit.net/**mailman/listinfo/cryptography<http://lists.randombit.net/mailman/listinfo/cryptography> >> > > > > -- > Leandro Federico Meiners > > _______________________________________________ > cryptography mailing list > cryptography@randombit.net > http://lists.randombit.net/mailman/listinfo/cryptography > >
_______________________________________________ cryptography mailing list cryptography@randombit.net http://lists.randombit.net/mailman/listinfo/cryptography
