strlcpy
Posted Jun 12, 2003 13:31 UTC (Thu) by
mrshiny (subscriber, #4266)
In reply to:
strlcpy by ncm
Parent article:
strlcpy
You are right; strlcpy can mask certain coding errors. But programmers always make errors; what's worse: a coding error that results in incorrect (but non-memory-corrupting) behaviour, or a coding error that results in a buffer overflow (which is usually guaranteed to be a sure path to denial of service or code injection)?
I'd rather have a programmer's mistakes masked as incorrect behaviour that won't allow attackers to take over my computer, thank you.
(
Log in to post comments)