OpenBSD Journal

DeveloperWorks piece on Buffer Overflows

Contributed by jose on from the education dept.

IBM DeveloperWorks has an article discussing the origins of buffer overflows in C and C++ development along with various mechanisms which prevent their successful exploitation. Among the remedies mentioned are ProPolice (originally developed by IBM, incorporated into the base system by OpenBSD in May, 2003) and safer APIs like strlcpy().

(Comments are closed)

  1. By some anonymous smartazz () on

    *comments on the lack of comments

  2. By clvrmnky () on

    Nice resource. The same author has written a HOWTO on safer C coding for UNIX. It looks pretty comprehensive, and is written in a very understandable manner.

    As luck would have it, I'm in the middle of doing some post-release maintenance on some legacy C code, and am probably going to audit the use of strcat() and strcpy() in this code for safety. The last few days have been a really and eye-opener for me. I've reviewed several references on safer C coding, and had some of my assumptions about the standard string library and pointers challenged.

    Of course, if I'd actually paid attention to the man pages, I'd have figured this out for myself. It's nice to have experts share their experience and show you how things can go pear-shaped.

    My C kung-fu is definitely stronger as a result.


Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]