4 Aug
2005
4 Aug
'05
11:03 p.m.
On 8/3/05, Robert E. Seastrom <rs@seastrom.com> wrote:
Michael.Dillon@btradianz.com writes:
We should all be looking to the security auditing work done by the OpenBSD team for an example of how systems can be cleaned up, fixed, and locked down if there is a will to do so.
Beer, unsupported assertions, and lack of rigorous audit methodology can be blended together to make one's code more secure?
what unsupported assertions? The project's record speaks for itself. Don't confuse Theo's lack of social graces with a lack of polish on the project he leads (a common mistake). -- darkuncle@{gmail.com,darkuncle.net} || 0x5537F527 encrypted email to the latter address please http://darkuncle.net/pubkey.asc for public key