Re: Xcode/gcc help in enforcing secure coding?
Re: Xcode/gcc help in enforcing secure coding?
- Subject: Re: Xcode/gcc help in enforcing secure coding?
- From: "Sean McBride" <email@hidden>
- Date: Tue, 15 Aug 2006 12:08:08 -0400
- Organization: Rogue Research
On 2006-08-15 17:23, Greg Hurrell said:
>Even though the misuse of these functions can lead to security
>problems (in the same way that the misuse of firearms can lead to
>people getting hurt), I don't think Apple or the GCC team will mark
>them as deprecated because they're not deprecated: they're defined in
>the standards. In the concrete example of strcat (brought up by the
>initial poster), it's defined in ISO/IEC 9899:1990 (ISO C90).
Well, gcc gives plenty of other warnings for plenty of completely
"acceptable" "standard" things, like unused variables, etc. We're
talking about warnings, not errors. Still, you make a good point.
Maybe instead of generating deprecated warnings, a new warning that
gives secure coding advice could be created...
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden