Re: Secure C programming
- From: Golden California Girls <GldnCAGrls@xxxxxxxxxxx>
- Date: Mon, 31 Dec 2007 11:46:14 -0800
Chris Thomasson wrote:
"Rico Secada" <coolzone@xxxxx> wrote in message
news:20071230223029.f17f1c63.coolzone@xxxxxxxx
Hi.
Doesn't there exist any complete texts on what to do and not do when
programming in C, from a security perspective?
Preferably with examples.
Don't program C if you don't know how to avoid common pitfalls; C gets a
bad rap sometimes. It's the fault of all the _lazy/crap_ programmers out
there which frequently create applications that do not even seem to have
any sense of where there buffer(s) begin, or _end_!!
Yikes! ;^(...
Think your finger is pointing in the wrong direction. Anyone who knows humans
knows that an IQ of 100 is average. A person who designs something that they
know will be used by an average person but doesn't design it for use by such a
person is the one who should have the fault heaped on them. When the standard
library and strings were defined, security may not have been an issue. Bad
future prediction I will forgive. However I can't forgive the standards people
for continuing to permit it. Depreciated should be enforced. Yes, break the
program or make them compile it under the old standard.
.
- Follow-Ups:
- Re: Secure C programming
- From: Randy Howard
- Re: Secure C programming
- From: Walter Roberson
- Re: Secure C programming
- References:
- Secure C programming
- From: Rico Secada
- Re: Secure C programming
- From: Chris Thomasson
- Secure C programming
- Prev by Date: Re: function returning days of the week
- Next by Date: Re: Making a program pause
- Previous by thread: Re: Secure C programming
- Next by thread: Re: Secure C programming
- Index(es):
Relevant Pages
|
