From: Sun Microsystems Sales Support <sun-sales-support@sun.com>
To: "David P. Quigley" <dpquigl@tycho.nsa.gov>
Cc: casey@schaufler-ca.com, sds@tycho.nsa.gov,
matthew.dodd@sparta.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
linux-security-module@vger.kernel.org, selinux@tycho.nsa.gov,
labeled-nfs@linux-nfs.org
Subject: RE: Re: [PATCH 08/14] NFSv4: Add label recommended attribute and NFSv4 flags (#6127-130006249-0129)
Date: Fri, 3 Apr 2009 10:33:27 -0700 (PDT) [thread overview]
Message-ID: <24068406.2060451238780007952.JavaMail.root@ms1b.instantservice.com> (raw)
-----Original Message-----
From: David P. Quigley (dpquigl@tycho.nsa.gov)
Sent: Apr 3, 2009 8:32:49 AM
Subject: Re: [PATCH 08/14] NFSv4: Add label recommended attribute and NFSv4 flags
On Fri, 2009-04-03 at 22:43 +1100, James Morris wrote:
> On Fri, 3 Apr 2009, David P. Quigley wrote:
>
> > We tried to change this to be dynamically allocated based on what was
> > coming off of the wire but we ran into a problem that it required us to
> > do allocations where they really shouldn't be done in the rpc/nfsv4
> > code. Trond suggested to make this static and that if someone really
> > needed more than a page for their label that something was horrifically
> > wrong. I'm tempted to agree with him on this but there are people trying
> > to send contexts with an MLS component with every other compartment set
> > which tend to be really large.
>
> Well, future labels might include cryptographic information, for example.
This report relates to a message you sent with the following header fields:
Message - ID: 134806025
From: dpquigl@tycho.nsa.gov
Subject: Re: [PATCH 08/14] NFSv4: Add label recommended attribute and NFSv4 flags
Your message cannot be delivered to the following recipients:
Recipient Address: Lawrence.Bowers@sun.com
Reason: This address is no longer available
>
<removing people from the CC who probably don't care about this>
Could you expand on why this might be needed or what applications would
use this? It's unclear to me what sort of crypto information would be in
a context. I know the ecryptfs guys were trying to make crypto decisions
based on SELinux context in some cases but I never heard of wanting to
put that kind of information into the context.
Dave
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
reply other threads:[~2009-04-03 17:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=24068406.2060451238780007952.JavaMail.root@ms1b.instantservice.com \
--to=sun-sales-support@sun.com \
--cc=casey@schaufler-ca.com \
--cc=dpquigl@tycho.nsa.gov \
--cc=labeled-nfs@linux-nfs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=matthew.dodd@sparta.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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
Powered by JetHome