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: "John C. Daub" <email@hidden>
- Date: Tue, 15 Aug 2006 08:31:54 -0500
- Thread-topic: Xcode/gcc help in enforcing secure coding?
on 8/15/06 2:46 AM, Jens Ayton at email@hidden wrote:
> John C. Daub:
>>
>> I was wondering if there's anything Xcode/gcc can currently do to help
>> enforce secure coding?
>>
>> I grant there's a lot here the compiler can't do, but for example take the
>> list of string functions to avoid:
>
> Copy the declarations into a file, say BadStuff.h. Then add
> __attribute__((deprecated)) or __attribute__((poison)) to each
> declaration. Include BadStuff.h from a prefix header.
Yeah, that's what Sean suggested (more or less).
I'd like to see system/standard-library functions (again, like those pointed
out in Apple's Secure Coding documentation) get this functionality so we can
all have better code "out of the box" than us all hacking our headers. :-)
Thanx.
--
John C. Daub }:-)>=
<mailto:email@hidden> <http://www.hsoi.com/>
"When taxes are too high, people go hungry.
When the government is too intrusive, people lose their spirit.
Act for the people's benefit.
Trust them; leave them alone." -- Tao Te Ching #75
_______________________________________________
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