Defensive programming: Difference between revisions

Revision as of 23:49, 7 August 2002

Revision as of 23:23, 26 January 2003

Line 1:

Here are some hints on '''defensive 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 (computing)|cracker]]

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