Re: Secure C programming
- From: jacob navia <jacob@xxxxxxxxxx>
- Date: Mon, 31 Dec 2007 12:01:37 +0100
Chris Thomasson wrote:
"jacob navia" <jacob@xxxxxxxxxx> wrote in message news:flaec9$6l5$2@xxxxxxxxxxxChris Thomasson wrote:[...]"Rico Secada" <coolzone@xxxxx> wrote in message news:20071230223029.f17f1c63.coolzone@xxxxxxxxHi.
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! ;^(...
Here we have the example of somebody that can't answer a simple
question and starts ranting for no reason.
Sorry about that. It just that C can be used to create bug-free programs. It takes a level of level that a lot of programmers don't seem to have...
Is that a radical line of thinking?
This is a much better answer. A person that wants to learn how
to program in C without doing the beginner's mistakes is well
server by a good book. And there are good ones, as many people
here have pointed out.
Thanks for clarifying your position.
--
jacob navia
jacob at jacob point remcomp point fr
logiciels/informatique
http://www.cs.virginia.edu/~lcc-win32
.
- References:
- Secure C programming
- From: Rico Secada
- Re: Secure C programming
- From: Chris Thomasson
- Re: Secure C programming
- From: jacob navia
- Re: Secure C programming
- From: Chris Thomasson
- Secure C programming
- Prev by Date: Uninitialised fields in structures
- Next by Date: Re: Uninitialised fields in structures
- Previous by thread: Re: Secure C programming
- Next by thread: Re: Secure C programming
- Index(es):
Relevant Pages
|