On Nov 29, 2007 5:13 PM, Andy Steingruebl <[EMAIL PROTECTED]> wrote: > I like contractual approaches to this problem myself. People buying > large quantities of software (large enterprises, governments) should > get contracts with vendors that specify money-back for each patch they > have to apply where the root cause is of a given type. For example, I > get money back every time the vendor has a vulnerability and patch > related to a buffer overflow. > > I wrote a small piece about this: > http://securityretentive.blogspot.com/2007/09/buffer-overflows-are-like-hospital.html
If you read Geekonomics, you'll find out why this may never happen. Because of existing software contracts, this is impossible today. David Rice dedicates chapter five to a discussion on this, but it also sprinkled throughout the book. Cheers, Andre _______________________________________________ Secure Coding mailing list (SC-L) SC-L@securecoding.org List information, subscriptions, etc - http://krvw.com/mailman/listinfo/sc-l List charter available at - http://www.securecoding.org/list/charter.php SC-L is hosted and moderated by KRvW Associates, LLC (http://www.KRvW.com) as a free, non-commercial service to the software security community. _______________________________________________
