From: Aaron Jones <aaronmdjones@gmail.com>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: File capabilities are not 'working' and I have no idea why
Date: Sun, 26 Jan 2014 16:28:59 +0000 [thread overview]
Message-ID: <52E537CB.40607@gmail.com> (raw)
In-Reply-To: <20140126162228.GA6946@mail.hallyn.com>
On 26/01/14 16:22, Serge E. Hallyn wrote:
> Hm, I'm running Ubuntu 3.13.0-5-generic and I do get
>
> serge@tp:~/test$ ./caps
> Effective capabilities:
> net_bind_service
> Permitted capabilities:
> net_bind_service
>
> Any chance (grasping for straws here) that the hardening patches
> are interfering? Can you try hand-building an upstream kernel to
> test with?
I downloaded a vanilla 3.12.8 tree directly from kernel.org
for the purposes of my previous post. I was running that kernel
then... I also have the same problem with the hardened kernel now.
I'm at a loss as to why it doesn't work on 3.12.8, but it does on
3.10.7, hardening patches or not.
next prev parent reply other threads:[~2014-01-26 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 13:25 File capabilities are not 'working' and I have no idea why Aaron Jones
2014-01-26 16:22 ` Serge E. Hallyn
2014-01-26 16:28 ` Aaron Jones [this message]
2014-02-04 19:18 ` Aaron Jones
2014-02-06 21:30 ` Serge E. Hallyn
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=52E537CB.40607@gmail.com \
--to=aaronmdjones@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=serge@hallyn.com \
/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