At 03:38 PM 8/10/00, Michael Paul Johnson wrote:
In case you haven't figured it out, yes, I am seriously contemplating
writing such a book.
There's certainly a need for defensive programming books oriented towards
security functions, and crypto functions in particular. On the other hand,
At 03:02 PM 8/11/00 -0400, John R Levine wrote:
All of the discussion of algorithms is fine, but it seems to me that the most
important topic in such a book is how to avoid building yet another crypto
system with a ten-ton steel door and a cardboard back wall. I would include
some horror stories
In case you haven't figured it out, yes, I am seriously contemplating
writing such a book. Please keep the good ideas coming.
Oh, good.
All of the discussion of algorithms is fine, but it seems to me that the most
important topic in such a book is how to avoid building yet another crypto
On Fri, 11 Aug 2000, John R Levine wrote:
* Don't try to invent a new crypto systems. Amateurs can't write secure
crypto systems, as often as not professionals can't either.
By the way, I would extend this to include "don't try to write your
own new crypto code, unless you really, really
At 04:00 PM 8/11/00 -0400, dmolnar wrote:
On Fri, 11 Aug 2000, John R Levine wrote:
* Don't try to invent a new crypto systems. Amateurs can't write secure
crypto systems, as often as not professionals can't either.
By the way, I would extend this to include "don't try to write your
own
