From: Pavel Machek <pavel@ucw.cz>
To: Ismail Kizir <ikizir@gmail.com>
Cc: Clemens Ladisch <clemens@ladisch.de>, linux-kernel@vger.kernel.org
Subject: Re: A new, fast and "unbreakable" encryption algorithm
Date: Thu, 3 Dec 2015 23:35:18 +0100 [thread overview]
Message-ID: <20151203223518.GF14427@amd> (raw)
In-Reply-To: <CAFJyfaOt5LR=icYCszCui1KTMGebhNZfx9XoonHhUKZejK7y7w@mail.gmail.com>
Hi!
> Check this out please; just visual proofs: Better than thousands of lines:
> http://ismail-kizir.blogspot.com.tr/2015/11/visual-proofs-of-hohha-dynamic-xor.html
Trouble is... it is hard to prove your encryption can not be broken,
but it is very easy to prove your encryption _can_ be broken. (*)
And it looks like Clemens did just that:
> > Anyway, I tried to modify your program to encrypt a large message
> > consisting only of zero bytes. The result did not look random.
Sorry.
Pavel
(*) And no, those pictures don't really prove anything.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-12-03 22:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 5:25 A new, fast and "unbreakable" encryption algorithm Ismail Kizir
2015-11-18 16:33 ` Harald Arnesen
2015-11-18 20:11 ` Ismail Kizir
2015-11-19 9:05 ` Clemens Ladisch
2015-11-21 6:31 ` Ismail Kizir
2015-12-03 22:35 ` Pavel Machek [this message]
2015-12-03 22:38 ` Ismail Kizir
2015-12-04 7:34 ` Clemens Ladisch
2015-12-04 9:42 ` Ismail Kizir
2015-12-04 15:28 ` Austin S Hemmelgarn
2015-11-19 2:35 ` Ismail Kizir
2015-11-19 12:12 ` Łukasz Stelmach
2015-11-19 12:31 ` Ismail Kizir
2015-11-19 14:04 ` Łukasz Stelmach
2015-11-19 14:05 ` Ismail Kizir
-- strict thread matches above, loose matches on Subject: below --
2015-11-18 5:10 Ismail Kizir
2015-11-18 19:31 ` Sandy Harris
2015-11-18 19:39 ` Ismail Kizir
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151203223518.GF14427@amd \
--to=pavel@ucw.cz \
--cc=clemens@ladisch.de \
--cc=ikizir@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.