Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1271852 > unrolled thread

A new, fast and "unbreakable" encryption algorithm

Back to article view | Back to linux.kernel

Contents

  A new, fast and "unbreakable" encryption algorithm Ismail Kizir <ikizir@gmail.com> - 2015-11-18 06:30 +0100
    Re: A new, fast and "unbreakable" encryption algorithm Harald Arnesen <harald@skogtun.org> - 2015-11-18 17:40 +0100
      Re: A new, fast and "unbreakable" encryption algorithm Ismail Kizir <ikizir@gmail.com> - 2015-11-18 21:20 +0100
        Re: A new, fast and "unbreakable" encryption algorithm Clemens Ladisch <clemens@ladisch.de> - 2015-11-19 10:10 +0100
          Re: A new, fast and "unbreakable" encryption algorithm Ismail Kizir <ikizir@gmail.com> - 2015-11-21 07:40 +0100
      Re: A new, fast and "unbreakable" encryption algorithm Ismail Kizir <ikizir@gmail.com> - 2015-11-19 03:40 +0100
    Re: A new, fast and "unbreakable" encryption algorithm Łukasz Stelmach <l.stelmach@samsung.com> - 2015-11-19 13:20 +0100
      Re: A new, fast and "unbreakable" encryption algorithm Ismail Kizir <ikizir@gmail.com> - 2015-11-19 13:40 +0100
        Re: A new, fast and "unbreakable" encryption algorithm Łukasz Stelmach <l.stelmach@samsung.com> - 2015-11-19 15:10 +0100
        Re: A new, fast and "unbreakable" encryption algorithm Ismail Kizir <ikizir@gmail.com> - 2015-11-19 15:10 +0100

#1271852 — A new, fast and "unbreakable" encryption algorithm

Hello,

I've developed a new encryption algorithm, which dynamically changes
the key according to plaintext and practically impossible to break. I
also opened to public with MIT&GPL dual License.
It is also quite fast; ~80% faster than the fastest mode of AES
without cpu instruction set support.
I will present a paper on a Turkish National Inet-tr 2015 Symposium on
3 December:
It is a very simple and yet efficient logic. Anyone who looks at the
self documented(in English) C code at
http://ismail-kizir.blogspot.com/2015/11/hohha-dynamic-xor-algorithm-source-code.html
 may understand why and how it is unbreakable.

I simply use the key as a jump table and, with every encrypted byte, I
change the jump table(the key) as a result of 3-4 parameters including
the last plaintext byte itself. Briefly, I encypt the plaintext with
the key and also dynamically encrypt the key with the plaintext.
The code is self documented in English.
On Linux simply
gcc HohhaDynamicXOR.c -O2 -Wall
./a.out
will make integrity checks and print benchmarks. It is production ready.
Other algorithm results are the output of the "openssl speed" command.
If I am right; you will not be disappointed to include "Hohha Dynamic
XOR Encryption Algorithm" on Linux Kernel.

I will be glad to see my algorithm included in Linux distributions.
Please feel free to ask if you have any questions.

Regards
Ismail Kizir
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1272360

Ismail Kizir [2015-11-18 06:25]:

> Hello,
> 
> I've developed a new encryption algorithm, which dynamically changes
> the key according to plaintext and practically impossible to break. I
> also opened to public with MIT&GPL dual License.

"There are two kinds of cryptography in this world: cryptography that
will stop your kid sister from reading your files, and cryptography that
will stop major governments from reading your files."
- Bruce Scheier, Applied Cryptography
-- 
Hilsen Harald
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1272532

Hello Harald,

I know that a lot of people thinks that there is a "new amateur in
town claiming having invented an unbreakable encryption" :)
That's why, I am trying to explain all my logic, publicly to professionals.
It's not rocket science. You will "just understand" when you read:

Until today, we were looking from the "wrong side" I guess.

We were all thinking that we must have a "fixed" key which must never change!

Why?

I begun to ask that question: "Why the key must be fixed?" and changed
the paradigm.

And I decided to dynamically update the key in encyption and decryption process.


The essential logic of the algorithm is using the key as a "jump
table" which is dynamically updated with every "jump" we make.

To understand better how it functions, suppose that we don't have a
complex function.


Given the key body length(L) is a power of 2, and M is an integer to
tell us where we are in the "key body":

We just take the byte at position M of the key body, we XOR that byte
with the byte to be encrypted(X).

We increase the byte at position M and "jump to" (M+X)%L


So, every time we encrypt a byte, we also change the key. It's a bit
more complicated than this. But essentially this is the base logic. In
real function, we do more complex operations with more variables like
the salt(or nonce) value, the last byte we encrypted, the key
checksum(against related key attacks) etc.

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!

I just want Linux uses a "strong encryption algorithm" to prevent
States, besides inalphabet kids, from reading your files :)

I believe this algorithm is the future of the encryption.

Source code: http://ismail-kizir.blogspot.com/2015/11/hohha-dynamic-xor-algorithm-source-code.html

Regards

On Wed, Nov 18, 2015 at 6:33 PM, Harald Arnesen <harald@skogtun.org> wrote:
> Ismail Kizir [2015-11-18 06:25]:
>
>> Hello,
>>
>> I've developed a new encryption algorithm, which dynamically changes
>> the key according to plaintext and practically impossible to break. I
>> also opened to public with MIT&GPL dual License.
>
> "There are two kinds of cryptography in this world: cryptography that
> will stop your kid sister from reading your files, and cryptography that
> will stop major governments from reading your files."
> - Bruce Scheier, Applied Cryptography
> --
> Hilsen Harald
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1272945

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1274607

Hello Clemens,

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

Regards
Ismail Kizir

On Thu, Nov 19, 2015 at 11:05 AM, Clemens Ladisch <clemens@ladisch.de> wrote:
> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1272752

I am not a cyrptoanalyst, not a mathematicien. But, I wanted to
enumerate some facts about "The Hohha Dynamic XOR Encryption"
algorithm I mentioned earlier.

My algorithm is "fundamentally different" from classical encryption
methods, because, it dynamically "encrypts" the key itself "during a
single transaction"!

"My Salt value" is a randomly choosen 4 bytes for every "transaction".
My "salt" is neither salt,  nor IV nor "salt in hashing", nor "nonce"
in cryptology, but a combination of all them.
Because:
The first jump position, depends on the salt value. Changing the
initial position of the encryption gives a "completely different
output"! This is a precaution against, chosen ciphertext attacks.
Not finished!
I XOR all bytes of salt value with 8Bit CRC, which give me a
"completely different output" for a small change in key, as I am using
those salt values for every byte to be encrypted. This is a precaution
against "related key attacks"
Changing the "salt value"(or call it nonce value if you prefer) of the
algorithm is not just a multiplication of possibilities by 255^4; but it also
"completely" changes the result. Because, it "completely" changes the
jump path!

The algorithm is safe against: Cryptoanalysis like : Index of
coincidence, Kasiski, Vigenere Cypher. Because, there is no "pattern".
For example the most frequent letter "A", of Turkish alphabet will be
encrpyted as different values each time.

Most importantly; during a single transaction, the plaintext is
encrypted with the key, meanwhile, the key itself is encrypted with
the plaintext. This avoids "chosen ciphertext" attack, "ciphertext
only attack" or  differential cryptoanalysis.

Even if salting is not used, the algorithm guarantees us that it is
impossible to find out the key even if we have the cyphertext and
plaintext. Because, "there will be a lack of information". Let's take
the trivial example: We do at least 2 jumps. So, we XOR the plaintext
byte with at least 2 numbers. In this case, even if we have the
plaintext and the cyphertext, we may just obtain the XOR result of 2
unknown values.

Regards
Ismail Kizir

On Wed, Nov 18, 2015 at 6:33 PM, Harald Arnesen <harald@skogtun.org> wrote:
> Ismail Kizir [2015-11-18 06:25]:
>
>> Hello,
>>
>> I've developed a new encryption algorithm, which dynamically changes
>> the key according to plaintext and practically impossible to break. I
>> also opened to public with MIT&GPL dual License.
>
> "There are two kinds of cryptography in this world: cryptography that
> will stop your kid sister from reading your files, and cryptography that
> will stop major governments from reading your files."
> - Bruce Scheier, Applied Cryptography
> --
> Hilsen Harald
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1273085

[Multipart message — attachments visible in raw view] — view raw

It was <2015-11-18 śro 06:25>, when Ismail Kizir wrote:
> Hello,
>
> I've developed a new encryption algorithm, which dynamically changes
> the key according to plaintext and practically impossible to break.
[...]
> I will be glad to see my algorithm included in Linux distributions.
> Please feel free to ask if you have any questions.

How resistant to side-channel attacts is or can be an implementation of
your algorithm? Not being an expert I am a bit worried about this
particular line 

    XORVal ^= *(Salt + (LastVal&(SALT_SIZE-1)));

which if I understand it correctly makes a memory access depending on
secret data. Because memory accesses are note constant time operations
due to cache one might try (and succeed?) learning about secrets by
measuring time required to encrypt or decrypt data.

-- 
Łukasz Stelmach
Samsung R&D Institute Poland
Samsung Electronics

[toc] | [prev] | [next] | [standalone]

#1273101

Francly Lucasz,

I am not an expert and never claimed it.
And I accept it's vulnerable to side channel attacks like the one you mentioned.
With this occasion, I want to emphasize one point:
I don't claim that the my algorithm is perfect.
But, take a look at this:

But, I am sure, this "dynamic key model" is the right way to follow
for the encyption.
You are all on the top of the "IT food chain" guys.
It is a GPLed algorithm and code.
Let's develop it ourselves for ourselves.
Let's think together.
For example; Clemens's "all zero" file is another weak point. I am
thinking about it too.
Help me. Criticise the algorithm.  wrote you all to be criticised.
Show me the weaknesses Let's think together and get it better.
Some people think that's not the right place for this discussions and
they may be right. Write me privately please. And I am constantly
updating the code on
http://ismail-kizir.blogspot.com.tr/2015/11/hohha-dynamic-xor-algorithm-source-code.html

Ismail Kizir
CTO, Hohha Internet Services Ltd.

On Thu, Nov 19, 2015 at 2:12 PM, Łukasz Stelmach <l.stelmach@samsung.com> wrote:
> It was <2015-11-18 śro 06:25>, when Ismail Kizir wrote:
>> Hello,
>>
>> I've developed a new encryption algorithm, which dynamically changes
>> the key according to plaintext and practically impossible to break.
> [...]
>> I will be glad to see my algorithm included in Linux distributions.
>> Please feel free to ask if you have any questions.
>
> How resistant to side-channel attacts is or can be an implementation of
> your algorithm? Not being an expert I am a bit worried about this
> particular line
>
>     XORVal ^= *(Salt + (LastVal&(SALT_SIZE-1)));
>
> which if I understand it correctly makes a memory access depending on
> secret data. Because memory accesses are note constant time operations
> due to cache one might try (and succeed?) learning about secrets by
> measuring time required to encrypt or decrypt data.
>
> --
> Łukasz Stelmach
> Samsung R&D Institute Poland
> Samsung Electronics
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1273155

[Multipart message — attachments visible in raw view] — view raw

It was <2015-11-19 czw 13:31>, when Ismail Kizir wrote:
> On Thu, Nov 19, 2015 at 2:12 PM, Łukasz Stelmach <l.stelmach@samsung.com> wrote:
>> It was <2015-11-18 śro 06:25>, when Ismail Kizir wrote:
>>> Hello,
>>>
>>> I've developed a new encryption algorithm, which dynamically changes
>>> the key according to plaintext and practically impossible to break.
>> [...]
>>> I will be glad to see my algorithm included in Linux distributions.
>>> Please feel free to ask if you have any questions.
>>
>> How resistant to side-channel attacts is or can be an implementation of
>> your algorithm? Not being an expert I am a bit worried about this
>> particular line
>>
>>     XORVal ^= *(Salt + (LastVal&(SALT_SIZE-1)));
>>
>> which if I understand it correctly makes a memory access depending on
>> secret data. Because memory accesses are note constant time operations
>> due to cache one might try (and succeed?) learning about secrets by
>> measuring time required to encrypt or decrypt data.
>
> I am not an expert and never claimed it.  And I accept it's vulnerable
> to side channel attacks like the one you mentioned.  With this
> occasion, I want to emphasize one point: I don't claim that the my
> algorithm is perfect. But, take a look at this:
>
> But, I am sure, this "dynamic key model" is the right way to follow
> for the encyption.

The issue I am attempting to point out is that even if mathematically an
algoritm is perfectly unbreakable (there is no easier way to recover
plaintext than a brute force attack) and its implementations are/can be
fast (in terms of clock cycles per encrypted byte) it may be of no
practical use because of possible side-channel attacks (the more
pracrical an attack the less usefull an algorithm/implementation).
Sometimes side-channel vulnerabilities can be fixed in software but they
need to be well understood.

IMHO if you want to "sell" your algorithm you need analyse its possible
side-channel weaknesses too. Moreover, if you'd like your algorithm to
become a part of Linux kernel I recomend you prepare a patch plugging it
properly into crypto/ directory.

Kind regards,
-- 
Łukasz Stelmach
Samsung R&D Institute Poland
Samsung Electronics

[toc] | [prev] | [next] | [standalone]

#1273157

Lukasz, Clemens, Herald, Others Linux and Open Source Enthusiasts:

You are all invited to collaboratively improve our encryption algorithm at:
https://github.com/ikizir/HohhaDynamicXOR

Write down every weaknesses you find, every idea to improve; every
code piece you think necessary.
Let us not disturb kernel group anymore.
Thank you very much in advance

On Thu, Nov 19, 2015 at 2:31 PM, Ismail Kizir <ikizir@gmail.com> wrote:
> Francly Lucasz,
>
> I am not an expert and never claimed it.
> And I accept it's vulnerable to side channel attacks like the one you mentioned.
> With this occasion, I want to emphasize one point:
> I don't claim that the my algorithm is perfect.
> But, take a look at this:
>
> But, I am sure, this "dynamic key model" is the right way to follow
> for the encyption.
> You are all on the top of the "IT food chain" guys.
> It is a GPLed algorithm and code.
> Let's develop it ourselves for ourselves.
> Let's think together.
> For example; Clemens's "all zero" file is another weak point. I am
> thinking about it too.
> Help me. Criticise the algorithm.  wrote you all to be criticised.
> Show me the weaknesses Let's think together and get it better.
> Some people think that's not the right place for this discussions and
> they may be right. Write me privately please. And I am constantly
> updating the code on
> http://ismail-kizir.blogspot.com.tr/2015/11/hohha-dynamic-xor-algorithm-source-code.html
>
> Ismail Kizir
> CTO, Hohha Internet Services Ltd.
>
> On Thu, Nov 19, 2015 at 2:12 PM, Łukasz Stelmach <l.stelmach@samsung.com> wrote:
>> It was <2015-11-18 śro 06:25>, when Ismail Kizir wrote:
>>> Hello,
>>>
>>> I've developed a new encryption algorithm, which dynamically changes
>>> the key according to plaintext and practically impossible to break.
>> [...]
>>> I will be glad to see my algorithm included in Linux distributions.
>>> Please feel free to ask if you have any questions.
>>
>> How resistant to side-channel attacts is or can be an implementation of
>> your algorithm? Not being an expert I am a bit worried about this
>> particular line
>>
>>     XORVal ^= *(Salt + (LastVal&(SALT_SIZE-1)));
>>
>> which if I understand it correctly makes a memory access depending on
>> secret data. Because memory accesses are note constant time operations
>> due to cache one might try (and succeed?) learning about secrets by
>> measuring time required to encrypt or decrypt data.
>>
>> --
>> Łukasz Stelmach
>> Samsung R&D Institute Poland
>> Samsung Electronics
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web