All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "David Prévot" <taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] fexecve.3: ffix
Date: Fri, 08 Nov 2013 05:55:26 +1300	[thread overview]
Message-ID: <527BC5FE.4060508@gmail.com> (raw)
In-Reply-To: <1383100652-7236-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>

Thanks, David. Applied.

Cheers,

Michael


On 10/30/13 15:37, David Prévot wrote:
> ---
>  man3/fexecve.3 | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/man3/fexecve.3 b/man3/fexecve.3
> index f228f00..03a00da 100644
> --- a/man3/fexecve.3
> +++ b/man3/fexecve.3
> @@ -114,7 +114,7 @@ Simply opening the file, checksumming the contents, and then doing an
>  would not suffice, since, between the two steps, the filename,
>  or a directory prefix of the pathname, could have been exchanged
>  (by, for example, modifying the target of a symbolic link).
> -.BR fexecve()
> +.BR fexecve ()
>  does not mitigate the problem that the
>  .I contents
>  of a file could be changed between the checksumming and the call to
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/

--
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

      parent reply	other threads:[~2013-11-07 16:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30  2:37 [PATCH] fexecve.3: ffix David Prévot
     [not found] ` <1383100652-7236-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2013-11-07 16:55   ` 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=527BC5FE.4060508@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=taffit-8fiUuRrzOP0dnm+yROfE0A@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.