RE: Writing Secure code

> > And one more thing...<this one might be intresting ;-)> Is it

The problem is not in writing code in which bugs are "totally prevented". It's in knowing that what you have written is bug (i.e. fault) -free. The only way to know this is to test your program with *all possible* inputs, which is impossible for all but the most trivial programs. Thus, you can never know that what you have written is in fact bug free. Unfortunately, this applies to writing secure programs as well. Sure, there are practices that we can utilize that will help us make our code more secure, but we can never be sure that is "totally secure".

Roger Alexander.

Roger T. Alexander
Associate Professor
Department of Computer Science
Colorado State University Received on Fri Dec 27 22:44:26 2002