Defensive programming: Difference between revisions

Revision as of 20:24, 26 February 2002

Revision as of 22:43, 21 June 2002

Line 1:

Here are some hints on codingdefensive programming techniques to avoid creating security problems.

Many of these techniques also improve general quality of code, because almost any major bug can be potentially used by a [[cracker]]

for a [[Denial of Service]] or other attack.

Note that the techniques below are ''not'' sufficient to ensure security: see the articles [[computer security]], [[computer insecurity]] and [[secure computing]] for more information.

<i>Please expand this article. These random notes should be changed to a more coherent article.</i>