All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eddie Kovsky <ewk@edkovsky.org>
To: Kees Cook <keescook@chromium.org>
Cc: Vaishali Thakkar <vaishali.thakkar@oracle.com>,
	"kernel-hardening@lists.openwall.com"
	<kernel-hardening@lists.openwall.com>
Subject: Re: [kernel-hardening] Getting started
Date: Thu, 2 Feb 2017 20:11:51 -0700	[thread overview]
Message-ID: <20170203031151.GA15897@athena> (raw)
In-Reply-To: <CAGXu5j+Ynmp3Z29_Zw6BG33P2RVi0eRtOiZR0incfoZBWF=7hg@mail.gmail.com>

On 01/30/17, Kees Cook wrote:
> On Mon, Jan 30, 2017 at 5:41 AM, Vaishali Thakkar
> <vaishali.thakkar@oracle.com> wrote:
> > On Monday 30 January 2017 12:13 AM, Eddie Kovsky wrote:
> >
> >> I'm interested in helping out with this project.
> >>
> >> I have a few small patches in the kernel. I just finished the Eudyptula
> >> Challenge and I'm looking for places where I can continue to contribute.
> 
> Hi! Welcome to the list. :)
> 
> >> I've been reading the list for several months now. I think I have a
> >> general
> >> understanding of the development process. Is there a specific TODO item I
> >> could start off with?
> 
> What areas of the kernel are you the most familiar with, and/or what
> things are you interested in working on? That could help me tailor
> some suggestions.
> 
> > Here, is one TODO list:
> >
> > https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project
> >
> > Although I think few people are already working on some of these things.
> > May be you can also check the archives of a mailing list.
> 
> The list is a bit terse (it's mostly been a brain dump as things come
> up), but yeah, if you see something there and want to know more, just
> ask. I'm happy to expand on any of them.
> 

I noticed there's been some activity recently with HARDENED_USERCOPY.
And I looked over how mm/usercopy.c was merged in from the grsecurity
patch. I'm curious about this TODO item:

     Identify and extend HARDENED_USERCOPY to other usercopy functions
     (e.g. maybe csum_partial_copy_from_user, csum_and_copy_from_user,
     csum_and_copy_to_user, csum_partial_copy_nocheck?)

It doesn't look like anyone is working on this task right now. But it's not
obvious (to me) what needs to happen to make progress with this. Would this
be a good task to start off with?

Thanks

Eddie

> Thanks!
> 
> -Kees
> 
> -- 
> Kees Cook
> Pixel Security

  reply	other threads:[~2017-02-03  3:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-29 18:43 [kernel-hardening] Getting started Eddie Kovsky
2017-01-30 13:41 ` Vaishali Thakkar
2017-01-30 21:44   ` Kees Cook
2017-02-03  3:11     ` Eddie Kovsky [this message]
2017-02-03  4:28       ` Vaishali Thakkar
2017-02-04  0:13         ` Kees Cook
2017-02-05 17:23           ` Vaishali Thakkar
2017-02-09  7:06     ` Djalal Harouni
2017-02-10 23:55       ` 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=20170203031151.GA15897@athena \
    --to=ewk@edkovsky.org \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=vaishali.thakkar@oracle.com \
    /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.