From: Daniel J Walsh <dwalsh@redhat.com>
To: Andrew Holway <andrew.holway@otternetworks.de>,
James Carter <jwcart2@tycho.nsa.gov>
Cc: "selinux@tycho.nsa.gov" <selinux@tycho.nsa.gov>
Subject: Re: NFS
Date: Fri, 19 Jun 2015 16:40:52 -0400 [thread overview]
Message-ID: <55847E54.1010802@redhat.com> (raw)
In-Reply-To: <CAEcA1_s34A+K3AtLkHAqjQF-hbt8t8TRDbrephf=f8S3Qx_5yg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]
On 06/19/2015 04:19 PM, Andrew Holway wrote:
>
>
> The v3 work was experimental and there was no real way to upstream
> it in a compatible way.
>
> Dave Quigley worked with the IETF on SELinux labeled NFS support
> for NFS 4.2 and it has been available since Fedora 20. This allows
> each file to have their own SELinux label on the server, but
> enforcement is only handled by the client.
>
>
> Does it work? :)
>
Yes as long as your client and server support the protocol. Currently I
know Fedora and RHEL7 do.
>
>
>
> --
> James Carter <jwcart2@tycho.nsa.gov>
> National Security Agency
> _______________________________________________
> Selinux mailing list
> Selinux@tycho.nsa.gov
> To unsubscribe, send email to Selinux-leave@tycho.nsa.gov.
> To get help, send an email containing "help" to
> Selinux-request@tycho.nsa.gov.
>
>
>
> --
> Otter Networks UG
> http://otternetworks.de
> fon: +49 30 54 88 5197
> Gotenstraße 17
> 10829 Berlin
>
>
>
> _______________________________________________
> Selinux mailing list
> Selinux@tycho.nsa.gov
> To unsubscribe, send email to Selinux-leave@tycho.nsa.gov.
> To get help, send an email containing "help" to Selinux-request@tycho.nsa.gov.
[-- Attachment #2: Type: text/html, Size: 3092 bytes --]
next prev parent reply other threads:[~2015-06-19 20:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 19:09 NFS Andrew Holway
2015-06-19 19:29 ` NFS James Carter
2015-06-19 20:19 ` NFS Andrew Holway
2015-06-19 20:40 ` Daniel J Walsh [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-13 14:13 Nfs Ina Flanagan
2003-11-15 21:23 nfs Redeeman
2003-11-15 21:48 ` nfs Hendrik Visage
2003-11-17 14:38 ` nfs Dan Oglesby
2003-11-17 4:08 ` nfs Hans Reiser
2003-11-17 16:38 ` nfs Eric Whiting
2003-11-17 17:16 ` nfs Redeeman
2003-08-23 17:35 nfs will supat
2003-08-05 6:36 nfs Rob Verduijn
2003-08-05 8:17 ` nfs Sven Riedel
2003-08-05 9:02 ` nfs Rob Verduijn
2003-08-05 9:49 ` nfs Chris Wilson
2003-08-07 0:58 ` nfs Ulises Hernandez Pino
2002-11-20 13:08 NFS ligp
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=55847E54.1010802@redhat.com \
--to=dwalsh@redhat.com \
--cc=andrew.holway@otternetworks.de \
--cc=jwcart2@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 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.