From: Clemens Ladisch <clemens@ladisch.de>
To: Ismail Kizir <ikizir@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: A new, fast and "unbreakable" encryption algorithm
Date: Thu, 19 Nov 2015 10:05:19 +0100 [thread overview]
Message-ID: <564D90CF.4080100@ladisch.de> (raw)
In-Reply-To: <CAFJyfaOzibRfaKhqvBh_yvQFfzQmO8e5wU4OK58g-my=TXwuSg@mail.gmail.com>
Ismail Kizir wrote:
> The essential logic of the algorithm is using the key as a "jump
> table" which is dynamically updated with every "jump" we make.
Sounds like RC4. Please tell us how you are avoiding the weaknesses
that make RC4 insecure.
> Briefly, to decypher a ciphertext, a cracker needs to find out the
> key, and, to find out the key, cracker needs to find out the
> plaintext, because the key is dynamically updated according the
> plaintext during encryption process: Impossible!
That problem has been solved for a long time:
https://en.wikipedia.org/wiki/Block_cipher_mode_of_operation
Anyway, I tried to modify your program to encrypt a large message
consisting only of zero bytes. The result did not look random.
Regards,
Clemens
next prev parent reply other threads:[~2015-11-19 9:05 UTC|newest]
Thread overview: 15+ 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 [this message]
2015-11-21 6:31 ` Ismail Kizir
2015-12-03 22:35 ` Pavel Machek
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
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=564D90CF.4080100@ladisch.de \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox