Re: Inspecting Code for Security

On Tue, 21 Sep 2004 20:57:51 +0200, "Aleksander P. Czarnowski" said:

> I would say that the final list of objectives should be business driven,

The truly hard part is that usually the very top item of the list is proclaimed
by somebody very high up the totem pole, and is a variant on:

"We must ship/deploy/whatever by next Thursday or we're screwed..."

Admittedly, it's somewhat off-topic for a "code inspection", but it's really
somewhat pointless to do the inspection if you don't have at least a foggy
idea of what you intend to do if you find a really bad gaping hole.

First Law of Systems Programming: "Never test for error conditions that
you don't know how to handle..."  :)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQFBUZWncC3lWbTT17ARAk7ZAJ0WKZIxxj0YHwJ3eKAGO5naHR5bcgCg7low
Fas16CfgMKAzt7p8/Qz6efI=
=k5cq
-----END PGP SIGNATURE-----