diff for duplicates of <6314EDD9-2B0F-454C-9B99-E57694DC7AE1@amacapital.net>
diff --git a/a/1.txt b/N1/1.txt
index 4b8759a..efb0661 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,11 +1,11 @@
-> On Feb 26, 2018, at 4:49 PM, Kees Cook <keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org> wrote:
+> On Feb 26, 2018, at 4:49 PM, Kees Cook <keescook@chromium.org> wrote:
>
->> On Wed, Feb 14, 2018 at 9:19 AM, Andy Lutomirski <luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org> wrote:
->>> On Wed, Feb 14, 2018 at 3:29 PM, Tycho Andersen <tycho-E0fblnxP3wo@public.gmane.org> wrote:
+>> On Wed, Feb 14, 2018 at 9:19 AM, Andy Lutomirski <luto@amacapital.net> wrote:
+>>> On Wed, Feb 14, 2018 at 3:29 PM, Tycho Andersen <tycho@tycho.ws> wrote:
>>>> On Tue, Feb 13, 2018 at 01:09:20PM -0800, Kees Cook wrote:
->>>> On Sun, Feb 4, 2018 at 2:49 AM, Tycho Andersen <tycho-E0fblnxP3wo@public.gmane.org> wrote:
+>>>> On Sun, Feb 4, 2018 at 2:49 AM, Tycho Andersen <tycho@tycho.ws> wrote:
>>>> I wonder if this communication should be netlink, which gives a more
>>>> well-structured way to describe what's on the wire? The reason I ask
>>>> is because if we ever change the seccomp_data structure, we'll now
diff --git a/a/content_digest b/N1/content_digest
index ae2bda6..f7e569f 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -17,10 +17,7 @@
"ref\0CAGXu5jKBmej+fXhEc+Jy7Guy+vXEZkHnc=4LNm1NNEsc1=DFVA\@mail.gmail.com\0"
]
[
- "ref\0CAGXu5jKBmej+fXhEc+Jy7Guy+vXEZkHnc=4LNm1NNEsc1=DFVA-JsoAwUIsXosN+BqQ9rBEUg\@public.gmane.org\0"
-]
-[
- "From\0Andy Lutomirski <luto-kltTT9wpgjJwATOyAt5JVQ\@public.gmane.org>\0"
+ "From\0Andy Lutomirski <luto\@amacapital.net>\0"
]
[
"Subject\0Re: [RFC 1/3] seccomp: add a return code to trap to userspace\0"
@@ -29,19 +26,22 @@
"Date\0Mon, 26 Feb 2018 19:27:51 -0800\0"
]
[
- "To\0Kees Cook <keescook-F7+t8E8rja9g9hUCZPvPmw\@public.gmane.org>\0"
+ "To\0Kees Cook <keescook\@chromium.org>\0"
]
[
- "Cc\0ast-DgEjT+Ai2ygdnm+yROfE0A\@public.gmane.org",
- " Linux Containers <containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA\@public.gmane.org>",
- " Akihiro Suda <suda.akihiro-Zyj7fXuS5i5L9jVzuh4AOg\@public.gmane.org>",
- " LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA\@public.gmane.org>",
- " Oleg Nesterov <oleg-H+wXaHxf7aLQT0dZR+AlfA\@public.gmane.org>",
- " Paul Moore <pmoore-H+wXaHxf7aLQT0dZR+AlfA\@public.gmane.org>",
- " Eric W . Biederman <ebiederm-aS9lmoZGLiVWk0Htik3J/w\@public.gmane.org>",
- " Sargun Dhillon <sargun-GaZTRHToo+CzQB+pC5nmwQ\@public.gmane.org>",
- " Christian Brauner <christian.brauner-GeWIH/nMZzLQT0dZR+AlfA\@public.gmane.org>",
- " Tyler Hicks <tyhicks-Z7WLFzj8eWMS+FvcfC7Uqw\@public.gmane.org>\0"
+ "Cc\0Tycho Andersen <tycho\@tycho.ws>",
+ " LKML <linux-kernel\@vger.kernel.org>",
+ " Linux Containers <containers\@lists.linux-foundation.org>",
+ " Oleg Nesterov <oleg\@redhat.com>",
+ " Eric W . Biederman <ebiederm\@xmission.com>",
+ " Serge E . Hallyn <serge\@hallyn.com>",
+ " Christian Brauner <christian.brauner\@ubuntu.com>",
+ " Tyler Hicks <tyhicks\@canonical.com>",
+ " Akihiro Suda <suda.akihiro\@lab.ntt.co.jp>",
+ " Tom Hromatka <tom.hromatka\@oracle.com>",
+ " Sargun Dhillon <sargun\@sargun.me>",
+ " Paul Moore <pmoore\@redhat.com>",
+ " ast\@kernel.org\0"
]
[
"\0000:1\0"
@@ -52,12 +52,12 @@
[
"\n",
"\n",
- "> On Feb 26, 2018, at 4:49 PM, Kees Cook <keescook-F7+t8E8rja9g9hUCZPvPmw\@public.gmane.org> wrote:\n",
+ "> On Feb 26, 2018, at 4:49 PM, Kees Cook <keescook\@chromium.org> wrote:\n",
"> \n",
- ">> On Wed, Feb 14, 2018 at 9:19 AM, Andy Lutomirski <luto-kltTT9wpgjJwATOyAt5JVQ\@public.gmane.org> wrote:\n",
- ">>> On Wed, Feb 14, 2018 at 3:29 PM, Tycho Andersen <tycho-E0fblnxP3wo\@public.gmane.org> wrote:\n",
+ ">> On Wed, Feb 14, 2018 at 9:19 AM, Andy Lutomirski <luto\@amacapital.net> wrote:\n",
+ ">>> On Wed, Feb 14, 2018 at 3:29 PM, Tycho Andersen <tycho\@tycho.ws> wrote:\n",
">>>> On Tue, Feb 13, 2018 at 01:09:20PM -0800, Kees Cook wrote:\n",
- ">>>> On Sun, Feb 4, 2018 at 2:49 AM, Tycho Andersen <tycho-E0fblnxP3wo\@public.gmane.org> wrote:\n",
+ ">>>> On Sun, Feb 4, 2018 at 2:49 AM, Tycho Andersen <tycho\@tycho.ws> wrote:\n",
">>>> I wonder if this communication should be netlink, which gives a more\n",
">>>> well-structured way to describe what's on the wire? The reason I ask\n",
">>>> is because if we ever change the seccomp_data structure, we'll now\n",
@@ -97,4 +97,4 @@
"Alexei, can we make it so that each bpf program type can easily limit which BPF_CALL helpers can be use and allow bpf program types to add their own helpers?c"
]
-403ccc20c00383a3dc04d6aa7b6e5b58b29a5848cca340c15b171fe737f217ee
+b4de67054024b4a68ce66af0828d4b4906c9397fa3c5ee917922136ac1cc9e8f
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.