On Thu, 2009-01-29 at 11:27 +0100, L. Aaron Kaplan wrote:
> Ok will do. But I prefer to have strcpy's etc out of the code somehow.

Most of the uses where after malloc()s and similar functions so they
were save - at least last time I looked at it.
And these cases ("strcpy()" after "malloc(strlen(s)+1)") are probably
better "fixed" sanely by using strdup() anyways.

[...]
> I mean - there is a reason why OpenBSD (a.k.a. the most paranoid OS in  

The question is if it's a *sane* reason.

> the world) does not like strcpy.

SICR: The trivial simple (and not that constructive) answer for the mgmt
level is: Perhaps they only have too many incompetent programmers (and
incompetent reviewers) there?
Perhaps they have inherited to much old code and failed to rewrite it
sanely over time?

Other than that, strlcpy() is the 1:1 replacement in the OpenBSD world
(and everyone can google for rants about the feature and misfeatures of
strncpy()).

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services




