1 .\" Copyright (c) 1989, 1991, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. All advertising materials mentioning features or use of this software
13 .\" must display the following acknowledgement:
14 .\" This product includes software developed by the University of
15 .\" California, Berkeley and its contributors.
16 .\" 4. Neither the name of the University nor the names of its contributors
17 .\" may be used to endorse or promote products derived from this software
18 .\" without specific prior written permission.
20 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32 .\" @(#)mktemp.3 8.1 (Berkeley) 6/4/93
33 .\" $FreeBSD: src/lib/libc/stdio/mktemp.3,v 1.20 2004/02/20 04:08:28 green Exp $
43 .Nd make temporary file name (unique)
70 takes the given file name template and overwrites a portion of it
71 to create a file name.
72 This file name is guaranteed not to exist at the time of function invocation
73 and is suitable for use
75 The template may be any file name with some number of
79 .Pa /tmp/temp.XXXXXX .
83 unique alphanumeric combination.
84 The number of unique file names
86 can return depends on the number of
93 selecting one of 56800235584 (62 ** 6) possible temporary file names.
98 makes the same replacement to the template and creates the template file,
99 mode 0600, returning a file descriptor opened for reading and writing.
100 This avoids the race between testing for a file's existence and opening it
105 function acts the same as
107 except it permits a suffix to exist in the template.
108 The template should be of the form
109 .Pa /tmp/tmpXXXXXXsuffix .
113 is told the length of the suffix string.
117 function makes the same replacement to the template as in
119 and creates the template directory, mode 0700.
125 functions return a pointer to the template on success and
133 return \-1 if no suitable file could be created.
134 If either call fails an error code is placed in the global variable
145 to one of the following values:
148 The pathname portion of the template is not an existing directory.
159 to any value specified by the
170 to any value specified by the
179 to any value specified by the
183 A common problem that results in a core dump is that the programmer
184 passes in a read-only string to
190 This is common with programs that were developed before
192 compilers were common.
196 .Qq /tmp/tempfile.XXXXXX
197 will result in a core dump due to
199 attempting to modify the string constant that was given.
200 If the program in question makes heavy use of that type
201 of function call, you do have the option of compiling the program
202 so that it will store string constants in a writable segment of memory.
205 for more information.
207 This family of functions produces filenames which can be guessed,
208 though the risk is minimized when large numbers of
211 increase the number of possible temporary filenames.
212 This makes the race in
214 between testing for a file's existence (in the
217 and opening it for use
218 (later in the user application)
219 particularly dangerous from a security perspective.
220 Whenever it is possible,
222 should be used instead, since it does not have the race condition.
225 cannot be used, the filename created by
227 should be created using the
231 and the return status of the call should be tested for failure.
232 This will ensure that the program does not continue blindly
233 in the event that an attacker has already created the file
234 with the intention of manipulating or reading its contents.
236 The implementation of these functions calls
238 which is not reentrant.
239 You must provide your own locking around this and other consumers of the
243 .Fd #include <unistd.h>
247 is necessary and sufficient for all functions.
266 function first appeared in
272 function first appeared in