[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5j+KYYRvWC1MmMyn3w1N5DsXeAnHR3wZvjpUfUaqd3L2Rw@mail.gmail.com>
Date: Wed, 25 Jan 2017 11:37:13 -0800
From: Kees Cook <keescook@...omium.org>
To: Jessica Frazelle <me@...sfraz.com>
Cc: "kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>
Subject: Re: Introduction
On Mon, Jan 23, 2017 at 4:06 PM, Jessica Frazelle <me@...sfraz.com> wrote:
> I've been lurking on this mailing list for over a year now, so I think
> I understand the gist of how it works. I am looking for some ways to
> help out in my free time.
Greetings! Thanks for saying "hi". :)
> The subsystems I know the most about are cgroups and namespaces. I
> previously was a maintainer of Docker (I added the seccomp integration
> and maintained the AppArmor bits) and now I work on kubernetes.
>
> Let me know if you think there is a good place to start!
I've mostly been trying to keep track of kernel self-protection TODO
items, so I haven't been keeping too up to date on userspace-support
things that the kernel provides. I know Solar has a list of things
he'd like to see, and I know there was an earlier attempt at building
an LSM to provide a more hardened chroot implementation (that Elena
sent a version of last year).
Are there any gaps in existing cgroups/namespaces stuff that you'd
like to see fixed? Or are there any areas of self-protection work that
you find interesting and would want to learn more about?
-Kees
--
Kees Cook
Nexus Security
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
