Hi all,

On around May first (International day of labour) I revisited some old code
of mine and published it.

I understand of the implications of a broken AES, but I'm an open person and
I believe that we must pull out quantum resistant and classic resistant
alternatives, because I have found cribs in AES.  Unfortunately this will
cause a hectic time I predict so bear with me.  I'm sharing it with the
OpenBSD community to help you get the word out on being the best OS in the
globe.  We all have our differences, but lets put egos aside and work together
not against each other.  We're facing a world that isn't so nice...

I would like to propose the following code changes in rijndael as a number
one:

In the function rijndaelEncrypt() in the following lines:

   930          s3 =
   931                  (Te2[(t3 >> 24)       ] & 0xff000000) ^
   932                  (Te3[(t0 >> 16) & 0xff] & 0x00ff0000) ^
   933                  (Te0[(t1 >>  8) & 0xff] & 0x0000ff00) ^
   934                  (Te1[(t2      ) & 0xff] & 0x000000ff) ^
   935                  rk[3];
   936          PUTU32(ct + 12, s3);
   937  }

Please consider adding a explicit_bzero() around all t* registers and stack
registers.  The reason for that is that this is 128 bits that can be used
to crack AES256 in brute force with 2^128 instead of 2^256.  I have a
inverted function for the r keytables.  As soon as these values are gotten
the cipher key is as good as cracked.  In a matter of a day, depending on
your hardware speed.  It can be scaled with lots and lots of computers
so all secrets can be read out in real time.

I have found a collision on a partial t0 value and I'm still doing research
on how to crack this.  However it doesn't seem impossible.

Best Regards,

-pjp (I love you)

-- 
my associated domains:  callpeter.tel|centroid.eu|dtschland.eu|mainrechner.de

Reply via email to