Defensive programming: Difference between revisions

Revision as of 02:35, 29 April 2004

Revision as of 22:53, 1 May 2004

Line 9:

-----------------------

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

* One of the most common problems is unchecked use of constant-size structures and functions for dynamic-size data (the [[buffer overflow]] problem). This is especially common for [[string]] data in [[C programming language|C]].

Line 16:

* Either leave your code available to everyone on the Net (see [[Free software]] or [[open source definition]]) or hire someone who will do [[security audit]] for you.

* If possible, reuse code instead of writing from scratch.

* Encrypt all important data thatwhich flowsflow the Net.

* All data is important until proved otherwise.

* All code is unsecure until proven otherwise.