|
NAMEmktemp —
make temporary file name (unique)
LIBRARYStandard C Library (libc, -lc)SYNOPSIS#include <stdlib.h>
char *
int
int
int
int
char *
int
DESCRIPTIONThemktemp () function takes the given file name template
and overwrites a portion of it to create a file name. This file name is
guaranteed not to exist at the time of function invocation and is suitable for
use by the application. The template may be any file name with some number of
‘Xs ’ appended to it, for example
/tmp/temp.XXXXXX. The trailing
‘Xs ’ are replaced with a unique
alphanumeric combination. The number of unique file names
mktemp () can return depends on the number of
‘Xs ’ provided; six
‘Xs ’ will result in
mktemp () selecting one of 56800235584 (62 ** 6)
possible temporary file names.
The The The The The RETURN VALUESThemktemp () and mkdtemp ()
functions return a pointer to the template on success and
NULL on failure. The
mkstemp (), mkostemp ()
mkstemps () and mkostemps ()
functions return -1 if no suitable file could be created. If either call fails
an error code is placed in the global variable errno.
ERRORSThemkstemp (), mkostemp (),
mkstemps (), mkostemps () and
mkdtemp () functions may set
errno to one of the following values:
The
The The The NOTESA common problem that results in a core dump is that the programmer passes in a read-only string tomktemp (),
mkstemp (), mkstemps () or
mkdtemp (). This is common with programs that were
developed before ISO/IEC 9899:1990
(“ISO C90”) compilers were common. For example,
calling mkstemp () with an argument of
“/tmp/tempfile.XXXXXX” will result in a core dump due to
mkstemp () attempting to modify the string constant
that was given.
The SEE ALSOchmod(2), getpid(2), mkdir(2), open(2), stat(2)STANDARDSThemkstemp () and mkdtemp ()
functions are expected to conform to IEEE Std 1003.1-2008
(“POSIX.1”). The mktemp ()
function is expected to conform to IEEE Std 1003.1-2001
(“POSIX.1”) and is not specified by IEEE
Std 1003.1-2008 (“POSIX.1”). The
mkostemp (), mkstemps (),
mkostemps () and mkostempsat ()
functions do not conform to any standard.
HISTORYAmktemp () function appeared in
Version 7 AT&T UNIX. The
mkstemp () function appeared in
4.4BSD. The mkdtemp () function
first appeared in OpenBSD 2.2, and later in
FreeBSD 3.2. The mkstemps ()
function first appeared in OpenBSD 2.4, and later in
FreeBSD 3.4. The mkostemp ()
and mkostemps () functions appeared in
FreeBSD 10.0. The
mkostempsat () function appeared in
FreeBSD 13.0.
BUGSThis family of functions produces filenames which can be guessed, though the risk is minimized when large numbers of ‘Xs ’ are used to increase the number of
possible temporary filenames. This makes the race in
mktemp (), between testing for a file's existence (in
the mktemp () function call) and opening it for use
(later in the user application) particularly dangerous from a security
perspective. Whenever it is possible, mkstemp (),
mkostemp () or mkostempsat ()
should be used instead, since they do not have the race condition. If
mkstemp () cannot be used, the filename created by
mktemp () should be created using the
O_EXCL flag to
open(2) and
the return status of the call should be tested for failure. This will ensure
that the program does not continue blindly in the event that an attacker has
already created the file with the intention of manipulating or reading its
contents.
Visit the GSP FreeBSD Man Page Interface. |