On Tue, 24 Aug 1999, Ben Pfaff wrote:
[ Debian uses a program called `mktemp' to create temporary files in
[ shell scripts. Other distributions might well adopt this or a similar
[ solution. An excerpt from its manpage is enclosed below.
RedHat includes a mktemp too, its a package by itself.
Funny how the man page does not say that this is derived from OpenBSD.
I'll include the new man page down below to show how we have improved
both the program and the manual page since. It's also good for people
to actually know what the flags mean.
Please note that it is /usr/bin/mktemp, not
Rogier Wolff writes:
Martin Schulze wrote:
This was not intentional by the author, he tried to use tempfile(1) to
create the temporary filename. However, due to a thinko, the name was
hardcoded into the script.
[...]
+#NNTPactive=\`tempfile -p active\` #"/tmp/active.\$\$"
So now
Martin Schulze wrote:
Rogier Wolff wrote:
Martin Schulze wrote:
This was not intentional by the author, he tried to use tempfile(1) to
create the temporary filename. However, due to a thinko, the name was
hardcoded into the script.
[...]
+#NNTPactive=\`tempfile -p active\`
Rogier Wolff wrote:
Martin Schulze wrote:
This was not intentional by the author, he tried to use tempfile(1) to
create the temporary filename. However, due to a thinko, the name was
hardcoded into the script.
[...]
+#NNTPactive=\`tempfile -p active\` #"/tmp/active.\$\$"
So now
Martin Schulze wrote:
Rogier Wolff wrote:
This was not intentional by the author, he tried to use tempfile(1) to
create the temporary filename. However, due to a thinko, the name was
hardcoded into the script.
[...]
+#NNTPactive=\`tempfile -p active\`
Richard Kettlewell [EMAIL PROTECTED] has reported a security
problem with trn. Trn comes with a newsgroups shell script that uses
a hardcoded filename in /tmp as temporary storage. As you all know,
this could be exploited to overwrite arbitrary files. If the file
already exists as symbolic
