From: Theodore Ts'o <tytso@mit.edu>
To: Jason Cooper <jason@lakedaemon.net>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Josh Boyer <jwboyer@fedoraproject.org>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] dev/maintainer workflow security
Date: Sat, 11 Jul 2015 12:38:38 -0400 [thread overview]
Message-ID: <20150711163838.GA4441@thunk.org> (raw)
In-Reply-To: <20150711160202.GC23515@io.lakedaemon.net>
On Sat, Jul 11, 2015 at 04:02:02PM +0000, Jason Cooper wrote:
>
> Could we have some sort of post-vuln/CVE conversation dissecting the
> vulnerability and how it got there? Or, perhaps select a few for
> process-dissection to be presented at the summit?
Kees did a really good presentation entitled "security anti-patterns"
a year or two ago at a kernel summit (the one at Edinburgh if I
remember correctly?). Kees, do you think it would be worth updating
and re-doing that presentation? And perhaps at a wider set of venues
beyond just the kernel summit....
- Ted
next prev parent reply other threads:[~2015-07-11 16:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 14:38 [Ksummit-discuss] [CORE TOPIC] dev/maintainer workflow security Jason Cooper
2015-07-10 15:50 ` Josh Boyer
2015-07-10 16:23 ` Theodore Ts'o
2015-07-10 19:45 ` Steven Rostedt
2015-07-10 20:34 ` Olof Johansson
2015-07-11 1:19 ` Jason Cooper
2015-07-10 22:08 ` Kees Cook
2015-07-11 1:48 ` Jason Cooper
2015-07-11 7:31 ` James Bottomley
2015-07-11 16:02 ` Jason Cooper
2015-07-11 16:38 ` Theodore Ts'o [this message]
2015-07-13 23:15 ` Kees Cook
2015-07-13 8:32 ` Jiri Kosina
2015-07-13 14:07 ` Konstantin Ryabitsev
2015-07-13 15:39 ` James Bottomley
2015-07-13 16:02 ` Mark Brown
2015-07-13 16:05 ` Konstantin Ryabitsev
2015-07-13 16:14 ` James Bottomley
2015-07-13 18:22 ` Theodore Ts'o
2015-07-13 16:46 ` Geert Uytterhoeven
2015-07-13 17:12 ` josh
2015-07-13 19:37 ` Jiri Kosina
2015-07-15 18:42 ` Steven Rostedt
2015-07-13 23:25 ` Kees Cook
2015-07-14 7:47 ` James Bottomley
2015-07-14 16:20 ` Kees Cook
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=20150711163838.GA4441@thunk.org \
--to=tytso@mit.edu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jason@lakedaemon.net \
--cc=jwboyer@fedoraproject.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/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.