Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hello,

I leafed through the definition of createTempFile in sal/inc/osl/file.hxx. I read this too : http://projects.cerias.purdue.edu/secprog/class2/6.Temp_&_Rand.ppt
"mktemp - generate temporary file name (unique)
mkstemp - also create the file
mkstemps - generate temporary file name with suffix
mkdtemp - create a directory
" and of course "no equivalent of these functions in Windows" for example.


So I thought this :
1) for common part between Windows and other systems (Unix/Linux/BSD and Mac) or for Windows specific, only createTempFile should be used. 2) for Unix/Linux/BSD and Mac only part, mkstemp/mktemp should be used (to avoid overhead)

So tmpnam shouldn't be used at all.

Is this ok ?

Julien.


-------- Message original --------
Sujet:  warning: the use of `tmpnam' is dangerous, better use `mkstemp'
Date :  Thu, 09 Jun 2011 23:24:16 +0200
De :    Julien Nabet <serval2412@yahoo.fr>
Pour :  libreoffice@lists.freedesktop.org



Hello,

I had this warning by compiling hwpfilter during some cppcheck cleaning.
I knew nothing about it so I read some links given by Google.
It seems mkstemp is safer since it permits "to avoid race conditions".

In the Unix man of tmpnam, we can read this :
"
BUGS
       Never use this function.  Use mkstemp(3) or tmpfile(3) instead.
"

I'm just a beginner in C++ so what's your opinion about it ?

Julien


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.