Recently, I’ve read an interesting article , explaining why the
strncpy function in C is not
strcpy. The post was very interesting, but what’s more, it suggested an alternative
idiom for copying strings in C, that might probably be the way to go.
Later, in another article  that compared some functionality in C, Python and Go, one of the comments pointed out that very same idiom. That grabbed my attention, so I decided to try it in an example.
The problem with
strncpy seems to be the way it manages the source string to be copied. Based on
the sample code provided in the documentation  (that should be just a reference), the break condition
is up to
n characters (the third parameter) or until the source string is exhausted, whatever happens first. This
should not be a problem, unless
n < strlen(source_string). That parameter would make
to finish before it can put a
\0 character at the end of the target string, leaving
an invalid array of characters .
This is an example.
On this example, the target array is represented by the variable
dst, and I used a fixed-length string,
on purpose for the demonstration, simulating what would actually happen. I null-terminated it so the program
can finish successfully, because otherwise the operations on it would not end until the delimiter is reached,
and we cannot know when that will happen, considering what’s in memory at that time. In addition, the
unpredictable behaviour will lead to errors, and probably to memory corruption. The underscore,
should be interpreted as slots: regions or reserved memory that are there, but empty.
The proposed idiom uses
strncat (see ),
tricking the function by passing it an empty string as the first parameter,
and then the actual string we need to copy. This call will render the same result,
but without the previous side effect.
Let’s see an example:
Here we see, the error is no longer present, probably because of the difference on the implementation (the snippet on the documentation  gives us a hint on what it does, so we can spot the change).
This might seem as a little issue, but it raised some concerns on the Linux kernel development, at the
point that a new function was developed. The
strscpy function is being included in the Kernel
development for Linux 4.3-rc4  because it is a better interface. Some of the problems mentioned
in the commit message, that inspired this new version, are the ones described on the previous paragraphs.
This makes me wonder, if this should be the “correct” way for performing this operation “safely” in C. In all
cases, the error is the same (not checking the boundaries, and trusting the input), and should be avoided. What I
mean by this, is that we cannot simply rely on those functions being secure, the security must be in our code,
so the proper way to handle these situations is to code defensively: do not trust user input, always check the boundaries,
error codes, memory allocation, status of the pointer (a
free for every
malloc but not for a
NULL pointer, etc.).
|||(1, 2) strncat manual page.|
|||An array of characters that is not null-terminated, is invalid.|