"Daniel L. Donahue" wrote: [cut]
(there are far too much packages to remember them all ;-))). Let's hope that the code of that one is better ... well, time to do a sourcecode audit :( *sigh*
Slightly off topic, but I've been hearing on and off about automated apps that search c source code for "gross violations" of a security nature (improper buffer checking comes to mind here) in the so called underworld. Well, do you mean tools such as ITS4 (http://www.rstcorp.com/its4/), which may help you doing an security audit. But I do not have any experiences with it. Marc? Thomas?
Anyway, there's a Secure Programming for Linux and Unix HOWTO (http://dwheeler.com/secure-programs/Secure-Programs-HOWTO.html) best regards, Rainer Link -- Rainer Link | Member of Virus Help Munich (www.vhm.haitec.de) rainer@w3.to | Member of AMaViS Development Team (amavis.org) rainer.w3.to | Maintainer FAQ "antivirus for Linux" (av-linux.w3.to)