1 .\" Copyright (C) 1993 David Metcalfe (david@prism.demon.co.uk)
3 .\" %%%LICENSE_START(verbatim)
4 .\" Permission is granted to make and distribute verbatim copies of this
5 .\" manual provided the copyright notice and this permission notice are
6 .\" preserved on all copies.
8 .\" Permission is granted to copy and distribute modified versions of this
9 .\" manual under the conditions for verbatim copying, provided that the
10 .\" entire resulting derived work is distributed under the terms of a
11 .\" permission notice identical to this one.
13 .\" Since the Linux kernel and libraries are constantly changing, this
14 .\" manual page may be incorrect or out-of-date. The author(s) assume no
15 .\" responsibility for errors or omissions, or for damages resulting from
16 .\" the use of the information contained herein. The author(s) may not
17 .\" have taken the same level of care in the production of this manual,
18 .\" which is licensed free of charge, as they might when working
21 .\" Formatted or processed versions of this manual, if unaccompanied by
22 .\" the source, must acknowledge the copyright and authors of this work.
25 .\" References consulted:
26 .\" Linux libc source code
27 .\" Lewine's _POSIX Programmer's Guide_ (O'Reilly & Associates, 1991)
29 .\" Modified Sat Jul 24 18:06:49 1993 by Rik Faith (faith@cs.unc.edu)
30 .\" Modified Fri Aug 25 23:17:51 1995 by Andries Brouwer (aeb@cwi.nl)
31 .\" Modified Wed Dec 18 00:47:18 1996 by Andries Brouwer (aeb@cwi.nl)
32 .\" 2007-06-15, Marc Boyer <marc.boyer@enseeiht.fr> + mtk
33 .\" Improve discussion of strncpy().
35 .TH STRCPY 3 2012-07-19 "GNU" "Linux Programmer's Manual"
37 strcpy, strncpy \- copy a string
40 .B #include <string.h>
42 .BI "char *strcpy(char *" dest ", const char *" src );
44 .BI "char *strncpy(char *" dest ", const char *" src ", size_t " n );
49 function copies the string pointed to by \fIsrc\fP,
50 including the terminating null byte (\(aq\\0\(aq),
51 to the buffer pointed to by \fIdest\fP.
52 The strings may not overlap, and the destination string
53 \fIdest\fP must be large enough to receive the copy.
54 .IR "Beware of buffer overruns!"
59 function is similar, except that at most
60 \fIn\fP bytes of \fIsrc\fP are copied.
62 If there is no null byte
63 among the first \fIn\fP bytes of \fIsrc\fP,
64 the string placed in \fIdest\fP will not be null-terminated.
71 writes additional null bytes to
73 to ensure that a total of
77 A simple implementation of
84 strncpy(char *dest, const char *src, size_t n)
88 for (i = 0; i < n && src[i] != \(aq\\0\(aq; i++)
91 dest[i] = \(aq\\0\(aq;
102 functions return a pointer to
103 the destination string \fIdest\fP.
105 SVr4, 4.3BSD, C89, C99.
107 Some programmers consider
109 to be inefficient and error prone.
110 If the programmer knows (i.e., includes code to test!)
111 that the size of \fIdest\fP is greater than
112 the length of \fIsrc\fP, then
116 One valid (and intended) use of
118 is to copy a C string to a fixed-length buffer
119 while ensuring both that the buffer is not overflowed
120 and that unused bytes in the target buffer are zeroed out
121 (perhaps to prevent information leaks if the buffer is to be
122 written to media or transmitted to another process via an
123 interprocess communication technique).
125 If there is no terminating null byte in the first \fIn\fP
128 produces an unterminated string in \fIdest\fP.
129 You can force termination using something like the following:
133 strncpy(buf, str, n);
135 buf[n \- 1]= \(aq\\0\(aq;
139 (Of course, the above technique ignores the fact that
140 information contained in
142 is lost in the copying to
145 Some systems (the BSDs, Solaris, and others) provide the following function:
147 size_t strlcpy(char *dest, const char *src, size_t size);
149 .\" http://static.usenix.org/event/usenix99/full_papers/millert/millert_html/index.html
150 .\" "strlcpy and strlcat - consistent, safe, string copy and concatenation"
151 .\" 1999 USENIX Annual Technical Conference
152 This function is similar to
154 but it copies at most
158 always adds a terminating null byte,
159 and does not pad the target with (further) null bytes.
160 This function fixes some of the problems of
164 but the caller must still handle the possibility of data loss if
167 The return value of the function is the length of
169 which allows truncation to be easily detected:
170 if the return value is greater than or equal to
173 If loss of data matters, the caller
175 either check the arguments before the call,
176 or test the function return value.
178 is not present in glibc and is not standardized by POSIX,
179 .\" https://lwn.net/Articles/506530/
180 but is available on Linux via the
184 If the destination string of a
186 is not large enough, then anything might happen.
187 Overflowing fixed-length string buffers is a favorite cracker technique
188 for taking complete control of the machine.
189 Any time a program reads or copies data into a buffer,
190 the program first needs to check that there's enough space.
191 This may be unnecessary if you can show that overflow is impossible,
192 but be careful: programs can get changed over time,
193 in ways that may make the impossible possible.