From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Gleb Fotengauer-Malinovskiy
<glebfm-u2l5PoMzF/Vg9hUCZPvPmw@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] mktemp.3: reference mkdtemp(3) in addition to mkstemp(3)
Date: Sat, 08 Aug 2015 10:08:29 +0200 [thread overview]
Message-ID: <55C5B8FD.8030108@gmail.com> (raw)
In-Reply-To: <20150808080512.GA7386-N9aU+Tdk7XkoO014n+3aBsY9il7ykmry@public.gmane.org>
On 08/08/2015 10:05 AM, Gleb Fotengauer-Malinovskiy wrote:
> Mention mkdtemp(3) as another secure alternative to mktemp(3).
>
> See also https://sourceware.org/bugzilla/show_bug.cgi?id=2898
Thanks, Gleb. Applied.
Cheers,
Michael
> ---
> man3/mktemp.3 | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/man3/mktemp.3 b/man3/mktemp.3
> index 79e9023..0531fad 100644
> --- a/man3/mktemp.3
> +++ b/man3/mktemp.3
> @@ -126,8 +126,10 @@ opening the file, every use of
> .BR mktemp ()
> is a security risk.
> The race is avoided by
> -.BR mkstemp (3).
> +.BR mkstemp (3) and
> +.BR mkdtemp (3).
> .SH SEE ALSO
> +.BR mkdtemp (3),
> .BR mkstemp (3),
> .BR tempnam (3),
> .BR tmpfile (3),
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-08-08 8:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 8:05 [PATCH] mktemp.3: reference mkdtemp(3) in addition to mkstemp(3) Gleb Fotengauer-Malinovskiy
[not found] ` <20150808080512.GA7386-N9aU+Tdk7XkoO014n+3aBsY9il7ykmry@public.gmane.org>
2015-08-08 8:08 ` Michael Kerrisk (man-pages) [this message]
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=55C5B8FD.8030108@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=glebfm-u2l5PoMzF/Vg9hUCZPvPmw@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).