From: "Serge E. Hallyn" <serge@hallyn.com>
To: KaiGai Kohei <kaigai.kohei@gmail.com>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-security-module@vger.kernel.org, chrisw@sous-sol.org
Subject: Re: [RFC] [PATCH] file posix capabilities
Date: Tue, 15 Aug 2006 07:04:19 -0500 [thread overview]
Message-ID: <20060815120419.GA7372@vino.hallyn.com> (raw)
In-Reply-To: <44E14406.7020208@ak.jp.nec.com>
Quoting KaiGai Kohei (kaigai.kohei@gmail.com):
> Hi,
>
> >>See
> >>http://www.kaigai.gr.jp/index.php?FrontPage#b556e50d
> >>http://www.kaigai.gr.jp/pub/fscaps-1.0-kg.src.rpm
> >>
> >>The later SRPM package includes the cap_file.c.
> >>It will be a good sample of using libcaps.
> >
> >And this has a version number built in, as Eric was asking for.
>
> _LINUX_CAPABILITY_VERSION defined as 0x19980330 is used for this.
> Is there a possibility to be changed future, isn't it?
> For example, when we think 32-bit width is not enough.
>
> >My tools were purely for testing, and just kept everything as simple as
> >possible. So I'll happily port the kernel patch to use your tools :)
> >
> >For that matter I see you have your own kernel patch. Would you mind
> >submitting that to lkml as an alternative to mine?
>
> I have no plan to submit now. It'll be called "Re-investment of wheel".
Assuming you meant reinvention, not at all. We want to get the best
patch in.
> # In addition, I'm currently busy to hack PostgreSQL. :D
Ok, well thanks for taking a look at this one.
> I hope to confirm one more point.
> Endian conpatibility is considered in the patches?
Not yet. Will add that and a check of the cap bitfield length as
mentioned in another email.
thanks,
-serge
next prev parent reply other threads:[~2006-08-15 12:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 1:13 Serge E. Hallyn
2006-08-14 22:06 ` Serge E. Hallyn
2006-08-15 0:20 ` Eric W. Biederman
2006-08-15 2:06 ` Serge E. Hallyn
2006-08-15 3:29 ` Eric W. Biederman
2006-08-15 4:22 ` Nicholas Miell
2006-08-15 11:49 ` Serge E. Hallyn
2006-08-15 12:20 ` Serge E. Hallyn
2006-08-15 19:31 ` Nicholas Miell
2006-08-15 19:41 ` Serge E. Hallyn
2006-08-15 16:18 ` Stephen Smalley
2006-08-15 16:36 ` Casey Schaufler
2006-08-16 2:42 ` Serge E. Hallyn
2006-08-16 13:20 ` Stephen Smalley
2006-08-17 12:00 ` Joshua Brindle
2006-08-17 12:28 ` Stephen Smalley
2006-08-21 20:36 ` Serge E. Hallyn
2006-08-28 21:39 ` Serge E. Hallyn
2006-08-29 18:37 ` Seth Arnold
2006-08-29 19:58 ` Serge E. Hallyn
2006-08-19 2:02 ` Crispin Cowan
2006-08-19 17:08 ` Casey Schaufler
2006-08-22 2:50 ` Serge E. Hallyn
2006-08-22 3:19 ` Seth Arnold
2006-08-19 2:02 ` Crispin Cowan
[not found] ` <44E1153D.9000102@ak.jp.nec.com>
[not found] ` <20060815021612.GC16220@sergelap.austin.ibm.com>
2006-08-15 3:48 ` KaiGai Kohei
2006-08-15 12:04 ` Serge E. Hallyn [this message]
2006-08-15 16:02 ` Casey Schaufler
2006-08-16 2:25 ` Serge E. Hallyn
2006-08-16 2:43 Albert Cahalan
2006-08-16 3:23 ` Serge E. Hallyn
2006-08-16 3:44 ` Casey Schaufler
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=20060815120419.GA7372@vino.hallyn.com \
--to=serge@hallyn.com \
--cc=chrisw@sous-sol.org \
--cc=ebiederm@xmission.com \
--cc=kaigai.kohei@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serue@us.ibm.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
all inboxes | Powered by JetHome®