linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Krzysztof Adamski <k@japko.eu>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] execve.2: EPERM from filesystem capabilities.
Date: Wed, 9 Mar 2016 01:49:41 +0100	[thread overview]
Message-ID: <56DF7325.9030702@gmail.com> (raw)
In-Reply-To: <20151012194506.GA6346-xLeyfSbClftGit24Ens98Q@public.gmane.org>

Hello Krzysztof

Sorry for the delayed follow up.

On 10/12/2015 09:45 PM, Krzysztof Adamski wrote:
> An EPERM error can be returned when using filesystem capabilities and
> capabilities to be added are not in permitted set.
> 
> This error return values was introduced by this patch:
> 5459c16 security: protect legacy applications from executing with
> insufficient privilege

Can you explain in more detail the scenario where EPERM can be produced.
I can't see/produce it. Also, the code in the commit that you mention,
which was part of Linux 2.6.27, was thoroughly changed in Linux 2.6.29.

Cheers,

Michael


> Signed-off-by: Krzysztof Adamski <k@japko.eu>
> ---
>  man2/execve.2 | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/man2/execve.2 b/man2/execve.2
> index 8f4c616..723e622 100644
> --- a/man2/execve.2
> +++ b/man2/execve.2
> @@ -465,6 +465,10 @@ and the file has the set-user-ID or set-group-ID bit set.
>  The process is being traced, the user is not the superuser and the
>  file has the set-user-ID or set-group-ID bit set.
>  .TP
> +.BR EPERM " (since Linux 2.6.27)"
> +The file has filesystem capabilities defined that are not on a permitted set of
> +capabilities of the process.
> +.TP
>  .B ETXTBSY
>  Executable was open for writing by one or more processes.
>  .SH CONFORMING TO
> 


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

  parent reply	other threads:[~2016-03-09  0:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12 19:45 [PATCH] execve.2: EPERM from filesystem capabilities Krzysztof Adamski
     [not found] ` <20151012194506.GA6346-xLeyfSbClftGit24Ens98Q@public.gmane.org>
2016-03-09  0:49   ` Michael Kerrisk (man-pages) [this message]
     [not found]     ` <56DF7325.9030702-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-03-09 20:15       ` Krzysztof Adamski
     [not found]         ` <20160309201501.GE25658-xLeyfSbClftGit24Ens98Q@public.gmane.org>
2016-03-10  0:33           ` Michael Kerrisk (man-pages)
     [not found]             ` <56E0C0C3.6040808-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-03-10 15:06               ` Krzysztof Adamski
     [not found]                 ` <20160310150633.GG25658-xLeyfSbClftGit24Ens98Q@public.gmane.org>
2016-03-10 17:07                   ` Michael Kerrisk (man-pages)
2016-04-05  3:25               ` Mike Frysinger

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=56DF7325.9030702@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=k@japko.eu \
    --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).