At 07:20 PM 8/11/00 +0000, lcs Mixmaster Remailer wrote:
>William Rowden writes:
>> In the tempting-but-wrong category, one could include samples of the
>> insecure systems that result when programmers with no cryptanalysis
>> background create their own cryptographic algorithms.
>
>Yes, and let us hope that Michael Paul Johnson resists the temptation to
>plug his own home-grown ciphers, Sapphire and Diamond. Hopefully he'll
>realize that including his own ciphers in the book will ruin what little
>credibility he has as an author.
Actually, I'd rather publish your credible cryptanalysis of those ciphers, if you care
to enlighten us. Lacking that, I'll see if I can egg someone else on to do so by
writing about them, too. I'm not as concerned about what one anonymous person thinks
about my credibility as I am about advancing the state of the art of computer
cryptography and making it more accessible to the average programmer. I think that
involves a balance where I will promote the best ciphers (i. e. the AES finalists),
but also explain the design, analysis, and limitations of my own ciphers. Who else
could explain them as well?
Seriously, if you know of a real weakness in either the Sapphire II Stream Cipher or
the Diamond 2 Block Cipher, please let us all know on this list, especially me. I
honestly don't know of one, but I openly admit that I could have missed something. Do
I write about these ciphers being victorious over your scrutiny, or about their
demise? Either one has value.
_______
Michael Paul Johnson
[EMAIL PROTECTED] http://ebible.org/mpj
