Re: Are bad developer libraries the problem with M$ software?

Frank Knobbe wrote:

> Perhaps we should start development of a standardized 'safe' header file

This works only with arrays. But breaks with pointers, because sizeof(pointer) returns 4 (32 bit machines) or 8 (64 bit machine)...

> Although it may be easier to rewrite the libraries with checks

that is snprintf() et al...

But these only give you the possibility to do something right. But to do it right you have to know what you are doing...

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related securityfocus.com Links bugtraq certification focus-bsd focus-ids focus-ih focus-linux focus-ms focus-sun focus-unix-other focus-virus forensics incidents libnet linux-secnews ms-secnews pen-test secpapers secprog sectools secureshell security-basics securityjobs sf-news vuln-dev webappsec Request more information about Pantek

> My argument is that we should move security into the libraries and tools

No.

The libraries must give the developer the tools he needs to write save programs.
Only he knows the limitations his program has and needs.

And it is his responsibility to implement these limitations.

Bye

Goetz

-- 
Goetz Babin-Ebell, TC TrustCenter AG, 
http://www.trustcenter.de
Sonninstr. 24-28, 20097 Hamburg, Germany
Tel.: +49-(0)40 80 80 26 -0,  Fax: +49-(0)40 80 80 26 -126