diff for duplicates of <564CC476.6090400@redhat.com> diff --git a/a/1.1.hdr b/a/1.1.hdr deleted file mode 100644 index fd1fee8..0000000 --- a/a/1.1.hdr +++ /dev/null @@ -1,2 +0,0 @@ -Content-Type: text/plain; charset=windows-1252 -Content-Transfer-Encoding: 7bit diff --git a/a/1.2.hdr b/a/1.2.hdr deleted file mode 100644 index 0a06a35..0000000 --- a/a/1.2.hdr +++ /dev/null @@ -1,3 +0,0 @@ -Content-Type: text/html; charset=windows-1252 -Content-Transfer-Encoding: quoted-printable -X-Mime-Autoconverted: from 8bit to quoted-printable by mime827 diff --git a/a/1.1.txt b/N1/1.txt similarity index 95% rename from a/1.1.txt rename to N1/1.txt index c289c10..5da504f 100644 --- a/a/1.1.txt +++ b/N1/1.txt @@ -89,10 +89,10 @@ On 11/18/2015 10:38 AM, Austin S Hemmelgarn wrote: > > _______________________________________________ > Selinux mailing list -> Selinux-+05T5uksL2qpZYMLLGbcSA@public.gmane.org -> To unsubscribe, send email to Selinux-leave-+05T5uksL2pAGbPMOrvdOA@public.gmane.org -> To get help, send an email containing "help" to Selinux-request-+05T5uksL2pAGbPMOrvdOA@public.gmane.org -From a safely/security point of view. I think you should focus on the +> 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. +>From a safely/security point of view. I think you should focus on the clear linux containers model for allowing containers on hosting providers. If we need "guaranteed" separation you really need to take advantage of kvm and each container using its own kernel. In standard diff --git a/a/1.2.bin b/N1/2.bin similarity index 93% rename from a/1.2.bin rename to N1/2.bin index ff1d3b3..2a065f9 100644 --- a/a/1.2.bin +++ b/N1/2.bin @@ -9,7 +9,7 @@ <div class="moz-cite-prefix">On 11/18/2015 10:38 AM, Austin S Hemmelgarn wrote:<br> </div> - <blockquote cite="mid:564C9B92.5080107-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" type="cite">On + <blockquote cite="mid:564C9B92.5080107@gmail.com" type="cite">On 2015-11-18 09:30, Seth Forshee wrote: <br> <blockquote type="cite">On Wed, Nov 18, 2015 at 07:46:53AM -0500, @@ -207,9 +207,9 @@ <br> <pre wrap="">_______________________________________________ Selinux mailing list -<a class="moz-txt-link-abbreviated" href="mailto:Selinux-+05T5uksL2pUKDJzkOSz4g@public.gmane.orgov">Selinux-+05T5uksL2qpZYMLLGbcSA@public.gmane.org</a> -To unsubscribe, send email to <a class="moz-txt-link-abbreviated" href="mailto:Selinux-leave-+05T5uksL2qpZYMLLGbcSA@public.gmane.org">Selinux-leave-+05T5uksL2qpZYMLLGbcSA@public.gmane.org</a>. -To get help, send an email containing "help" to <a class="moz-txt-link-abbreviated" href="mailto:Selinux-request-+05T5uksL2qpZYMLLGbcSA@public.gmane.org">Selinux-request-+05T5uksL2qpZYMLLGbcSA@public.gmane.org</a>.</pre> +<a class="moz-txt-link-abbreviated" href="mailto:Selinux@tycho.nsa.gov">Selinux@tycho.nsa.gov</a> +To unsubscribe, send email to <a class="moz-txt-link-abbreviated" href="mailto:Selinux-leave@tycho.nsa.gov">Selinux-leave@tycho.nsa.gov</a>. +To get help, send an email containing "help" to <a class="moz-txt-link-abbreviated" href="mailto:Selinux-request@tycho.nsa.gov">Selinux-request@tycho.nsa.gov</a>.</pre> </blockquote> From a safely/security point of view. I think you should focus on the clear linux containers model for allowing containers on hosting diff --git a/a/2.hdr b/N1/2.hdr index 4b86001..0a06a35 100644 --- a/a/2.hdr +++ b/N1/2.hdr @@ -1,4 +1,3 @@ -Content-Type: text/plain; charset="us-ascii" -MIME-Version: 1.0 -Content-Transfer-Encoding: 7bit -Content-Disposition: inline +Content-Type: text/html; charset=windows-1252 +Content-Transfer-Encoding: quoted-printable +X-Mime-Autoconverted: from 8bit to quoted-printable by mime827 diff --git a/a/2.txt b/a/2.txt deleted file mode 100644 index f796da2..0000000 --- a/a/2.txt +++ /dev/null @@ -1,5 +0,0 @@ -_______________________________________________ -Selinux mailing list -Selinux-+05T5uksL2qpZYMLLGbcSA@public.gmane.org -To unsubscribe, send email to Selinux-leave-+05T5uksL2pAGbPMOrvdOA@public.gmane.org -To get help, send an email containing "help" to Selinux-request-+05T5uksL2pAGbPMOrvdOA@public.gmane.org diff --git a/a/content_digest b/N1/content_digest index 8fe381d..a248854 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -10,25 +10,24 @@ "ref\0564C733D.7010601@gmail.com\0" "ref\020151118143022.GC134139@ubuntu-hedt\0" "ref\0564C9B92.5080107@gmail.com\0" - "ref\0564C9B92.5080107-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org\0" - "From\0Daniel J Walsh <dwalsh-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>\0" + "From\0Daniel J Walsh <dwalsh@redhat.com>\0" "Subject\0Re: [PATCH v3 0/7] User namespace mount updates\0" "Date\0Wed, 18 Nov 2015 13:33:26 -0500\0" - "To\0Austin S Hemmelgarn <ahferroin7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>" - " Seth Forshee <seth.forshee-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>\0" - "Cc\0linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" - Serge Hallyn <serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org> - Theodore Ts'o <tytso-3s7WtUTddSA@public.gmane.org> - dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org - linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org - Andy Lutomirski <luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org> - linux-raid-u79uwXL29TY76Z2rM5mHXA@public.gmane.org - linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org - linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org - Al Viro <viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org> - selinux-+05T5uksL2qpZYMLLGbcSA@public.gmane.org - " linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\0" - "\02:1.1\0" + "To\0Austin S Hemmelgarn <ahferroin7@gmail.com>" + " Seth Forshee <seth.forshee@canonical.com>\0" + "Cc\0linux-security-module@vger.kernel.org" + Theodore Ts'o <tytso@mit.edu> + Serge Hallyn <serge.hallyn@canonical.com> + linux-kernel@vger.kernel.org + dm-devel@redhat.com + Andy Lutomirski <luto@amacapital.net> + linux-raid@vger.kernel.org + linux-bcache@vger.kernel.org + linux-mtd@lists.infradead.org + Al Viro <viro@zeniv.linux.org.uk> + selinux@tycho.nsa.gov + " linux-fsdevel@vger.kernel.org\0" + "\01:1\0" "b\0" "\n" "\n" @@ -121,16 +120,16 @@ ">\n" "> _______________________________________________\n" "> Selinux mailing list\n" - "> Selinux-+05T5uksL2qpZYMLLGbcSA@public.gmane.org\n" - "> To unsubscribe, send email to Selinux-leave-+05T5uksL2pAGbPMOrvdOA@public.gmane.org\n" - "> To get help, send an email containing \"help\" to Selinux-request-+05T5uksL2pAGbPMOrvdOA@public.gmane.org\n" - "From a safely/security point of view. I think you should focus on the\n" + "> Selinux@tycho.nsa.gov\n" + "> To unsubscribe, send email to Selinux-leave@tycho.nsa.gov.\n" + "> To get help, send an email containing \"help\" to Selinux-request@tycho.nsa.gov.\n" + ">From a safely/security point of view. I think you should focus on the\n" "clear linux containers model for allowing containers on hosting\n" "providers. If we need \"guaranteed\" separation you really need to take\n" "advantage of kvm and each container using its own kernel. In standard\n" "containers if a process can talk directly to the host kernel, any kernel\n" bug could potentially allow a break out. - "\02:1.2\0" + "\01:2\0" "b\0" "<html>\r\n" " <head>\r\n" @@ -143,7 +142,7 @@ " <div class=\"moz-cite-prefix\">On 11/18/2015 10:38 AM, Austin S\r\n" " Hemmelgarn wrote:<br>\r\n" " </div>\r\n" - " <blockquote cite=\"mid:564C9B92.5080107-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org\" type=\"cite\">On\r\n" + " <blockquote cite=\"mid:564C9B92.5080107@gmail.com\" type=\"cite\">On\r\n" " 2015-11-18 09:30, Seth Forshee wrote:\r\n" " <br>\r\n" " <blockquote type=\"cite\">On Wed, Nov 18, 2015 at 07:46:53AM -0500,\r\n" @@ -341,9 +340,9 @@ " <br>\r\n" " <pre wrap=\"\">_______________________________________________\r\n" "Selinux mailing list\r\n" - "<a class=\"moz-txt-link-abbreviated\" href=\"mailto:Selinux-+05T5uksL2pUKDJzkOSz4g@public.gmane.orgov\">Selinux-+05T5uksL2qpZYMLLGbcSA@public.gmane.org</a>\r\n" - "To unsubscribe, send email to <a class=\"moz-txt-link-abbreviated\" href=\"mailto:Selinux-leave-+05T5uksL2qpZYMLLGbcSA@public.gmane.org\">Selinux-leave-+05T5uksL2qpZYMLLGbcSA@public.gmane.org</a>.\r\n" - "To get help, send an email containing \"help\" to <a class=\"moz-txt-link-abbreviated\" href=\"mailto:Selinux-request-+05T5uksL2qpZYMLLGbcSA@public.gmane.org\">Selinux-request-+05T5uksL2qpZYMLLGbcSA@public.gmane.org</a>.</pre>\r\n" + "<a class=\"moz-txt-link-abbreviated\" href=\"mailto:Selinux@tycho.nsa.gov\">Selinux@tycho.nsa.gov</a>\r\n" + "To unsubscribe, send email to <a class=\"moz-txt-link-abbreviated\" href=\"mailto:Selinux-leave@tycho.nsa.gov\">Selinux-leave@tycho.nsa.gov</a>.\r\n" + "To get help, send an email containing \"help\" to <a class=\"moz-txt-link-abbreviated\" href=\"mailto:Selinux-request@tycho.nsa.gov\">Selinux-request@tycho.nsa.gov</a>.</pre>\r\n" " </blockquote>\r\n" " From a safely/security point of view. I think you should focus on\r\n" " the clear linux containers model for allowing containers on hosting\r\n" @@ -353,12 +352,5 @@ " kernel, any kernel bug could potentially allow a break out.<br>\r\n" " </body>\r\n" "</html>\r\n" - "\01:2\0" - "b\0" - "_______________________________________________\n" - "Selinux mailing list\n" - "Selinux-+05T5uksL2qpZYMLLGbcSA@public.gmane.org\n" - "To unsubscribe, send email to Selinux-leave-+05T5uksL2pAGbPMOrvdOA@public.gmane.org\n" - "To get help, send an email containing \"help\" to Selinux-request-+05T5uksL2pAGbPMOrvdOA@public.gmane.org" -722a514963216b0c76ba920830025a2adf395cba4976c72352881f7cecfc060f +3ab74ee15b3c5ba944689bf20b0cbac677703d9d44ccbdd64dd4a85cd148f8aa
diff --git a/a/1.1.txt b/N2/1.1.txt index c289c10..c61d6d4 100644 --- a/a/1.1.txt +++ b/N2/1.1.txt @@ -92,7 +92,7 @@ On 11/18/2015 10:38 AM, Austin S Hemmelgarn wrote: > Selinux-+05T5uksL2qpZYMLLGbcSA@public.gmane.org > To unsubscribe, send email to Selinux-leave-+05T5uksL2pAGbPMOrvdOA@public.gmane.org > To get help, send an email containing "help" to Selinux-request-+05T5uksL2pAGbPMOrvdOA@public.gmane.org -From a safely/security point of view. I think you should focus on the +>From a safely/security point of view. I think you should focus on the clear linux containers model for allowing containers on hosting providers. If we need "guaranteed" separation you really need to take advantage of kvm and each container using its own kernel. In standard diff --git a/a/content_digest b/N2/content_digest index 8fe381d..dcf3c4f 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -124,7 +124,7 @@ "> Selinux-+05T5uksL2qpZYMLLGbcSA@public.gmane.org\n" "> To unsubscribe, send email to Selinux-leave-+05T5uksL2pAGbPMOrvdOA@public.gmane.org\n" "> To get help, send an email containing \"help\" to Selinux-request-+05T5uksL2pAGbPMOrvdOA@public.gmane.org\n" - "From a safely/security point of view. I think you should focus on the\n" + ">From a safely/security point of view. I think you should focus on the\n" "clear linux containers model for allowing containers on hosting\n" "providers. If we need \"guaranteed\" separation you really need to take\n" "advantage of kvm and each container using its own kernel. In standard\n" @@ -361,4 +361,4 @@ "To unsubscribe, send email to Selinux-leave-+05T5uksL2pAGbPMOrvdOA@public.gmane.org\n" "To get help, send an email containing \"help\" to Selinux-request-+05T5uksL2pAGbPMOrvdOA@public.gmane.org" -722a514963216b0c76ba920830025a2adf395cba4976c72352881f7cecfc060f +b9974b33cb2ed59d501d00c2f10c58579632b1d01049fada2e4e51d5ab0ca53a
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.