So sprach [EMAIL PROTECTED] am Sun, Jun 17, 2001 at 01:26:11PM +0200:
> >The mktemp binary is nothing more than a wrapper to the C function mktemp,
> >which conforms to BSD 4.3, at least according to mktemp(3).
>
> But mktemp does not do anything different from the method I proposed.
From man mktemp:
| mktemp is provided to allow shell scripts to safely use temporary files.
| Traditionally, many shell scripts take the name of the program with the PID
| as a suffix and use that as a temporary file name. This kind of naming
| scheme is predictable and the race condition it creates is easy for an
| attacker to win. A safer, though still inferior approach is to make a
| temporary directory using the same naming scheme. While this does allow one
| to guarantee that a temporary file will not be subverted, it still allows a
| simple denial of service attack. For these reasons it is suggested that
| mktemp be used instead.
> mktemp has been designed for a OS with a 14 byte filename limit,
> current OS have 255, so thee is no need to use a program that
> has only one improvement compared to the shell method: a shorter
> filename.
You are talking about the $$ way of creating temp files, aren't you?
Or, in how far is /tmp/A_Quite_Long_Filename_Made_With_mktemp_b0RaZe shorter
than what you can do with the shell (the 'b0RaZe' was made by mktemp)?
Alexander Skwar
--
How to quote: http://learn.to/quote (german) http://quote.6x.to (english)
Homepage: http://www.digitalprojects.com | http://www.iso-top.de
iso-top.de - Die g�nstige Art an Linux Distributionen zu kommen
Uptime: 19 hours 57 minutes
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
