From: Progga <abulfazl@juniv.edu>
To: linux-c-programming@vger.kernel.org
Subject: Re: mktemp()
Date: Sat, 5 Jun 2004 14:17:05 +0600 [thread overview]
Message-ID: <20040605141705.A681@Imrashi.net.bd> (raw)
In-Reply-To: <16577.21054.198004.325948@cerise.nosuchdomain.co.uk>; from glynn.clements@virgin.net on Sat, Jun 05, 2004 at 05:55:26AM +0100
On Sat, Jun 05, 2004 at 05:55:26AM +0100, Glynn Clements wrote:
>
> The risk is that, if you don't use O_EXCL, an attacker could create a
> symlink between the point that mktemp() returns and the point that you
> call open/fopen/etc, causing you to overwrite the target of the
> symlink.
Does the above mean that mktemp( "abcXXXXXX" ) can return "abc123456" even if
there's a symlink with the name "abc123456" ?
Khoda Hafez
Progga
next prev parent reply other threads:[~2004-06-05 8:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-05 3:30 mktemp() Progga
2004-06-05 4:55 ` mktemp() Glynn Clements
2004-06-05 8:17 ` Progga [this message]
2004-06-05 11:16 ` mktemp() Jan-Benedict Glaw
2004-06-05 12:40 ` mktemp() Progga
2004-06-05 13:18 ` mktemp() Jan-Benedict Glaw
2004-06-05 19:42 ` mktemp() Glynn Clements
2004-06-05 22:43 ` mktemp() Progga
2004-06-06 9:50 ` mktemp() Martin Olsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040605141705.A681@Imrashi.net.bd \
--to=abulfazl@juniv.edu \
--cc=linux-c-programming@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).