Insecure Programming by example

[aarklon]

Hi folks,

found an interesting C link here::
http://community.core-sdi.com/~gera/InsecureProgramming/

 

[Richard Heathfield]

(e-mail address removed) said:

Hi folks,

found an interesting C link here::
http://community.core-sdi.com/~gera/InsecureProgramming/

I looked at the first example. Anyone programming like that needs a good
kicking.

 

[Eric Sosman]

(e-mail address removed) said:




I looked at the first example. Anyone programming like that needs a good
kicking.

It's interesting that the example indulges in undefined
behavior (twice!) before arriving at what was probably the
point it was trying to make. One doesn't know whether the
author deserves praise or blame.

 

[bluejack]

It's interesting that the example indulges in undefined
behavior (twice!) before arriving at what was probably the
point it was trying to make. One doesn't know whether the
author deserves praise or blame.

Similarly, all the argc and argv parameter conventions are reversed; is
that ignorance? or some sort of erudite gotcha for improperly trained
applicants? The whole thing feels like a red herring: which of the many
objectionable elements am I *supposed* to be objecting to... ?

 

[aarklon]

Hi all,

here are some more interesting links::-


http://www.cs.berkeley.edu/~ushankar/research/percents/percents.html
http://www.cs.dartmouth.edu/~cs38/local/formats-teso.html

 

[Richard Heathfield]

(e-mail address removed) said:

Hi all,

here are some more interesting links::-


http://www.cs.berkeley.edu/~ushankar/research/percents/percents.html

I have the very greatest of respect for David Wagner's cryptographic skills.
I would not ask him to write C code for me. (Sorry, David, if you ever read
this!)

http://www.cs.dartmouth.edu/~cs38/local/formats-teso.html

Whoever wrote that needs a good kicking. Here's a quote:

++++
A format string is an ASCIIZ string that contains text and format parame-
ters.Example:

printf ("The magic number is: %s\n", 1911);
++++

In this tiny fragment, which is the first significant bit of C code in the
document, I count two oopses - one in the text and one in the code. Oops.