From: Kees Cook <keescook@chromium.org>
To: Kassad <aashad940@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>, kernel-hardening@lists.openwall.com
Subject: Re: Contributing to KSPP newbie
Date: Sat, 30 Nov 2019 09:11:36 -0800 [thread overview]
Message-ID: <201911300855.BC12761@keescook> (raw)
In-Reply-To: <CA+OAcEO8TnqLTBoCUjP=-z4TCrTTHqXx4pY7mBj+FZ0pAvw8XA@mail.gmail.com>
On Fri, Nov 29, 2019 at 12:32:17PM -0500, Kassad wrote:
> On Fri, Nov 29, 2019 at 6:29 AM Mark Rutland <mark.rutland@arm.com> wrote:
> > On Thu, Nov 28, 2019 at 11:39:11PM -0500, Kassad wrote:
> > > Hey Kees,
> > >
> > > I'm 3rd university student interested in learning more about the linux kernel.
> > > I'm came across this subsystem, since it aligns with my interest in security.
Hi! Welcome to the list. :)
> > > Do you think as a newbie this task
> > https://github.com/KSPP/linux/issues/11 will
> > > be a good starting point?
> >
> > I think this specific task (Disable arm32 kuser helpers) has already
> > been done, and the ticket is stale.
>
> This might be a bit to vague but is there any task that is beginner
> friendly? I did have a look at todo list and most of them look quite
> daunting.
I tried marking some bugs with "good first issue", but it looks like
people are already chipping away at things:
https://github.com/KSPP/linux/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22
I haven't checked on this thread of discussion recently:
https://lore.kernel.org/lkml/CANhBUQ3V2A-TBVizVh+eMLSi5Gzw5sMBY7C-0a8=-z15qyQ75w@mail.gmail.com/
There might be some work in there still to replace odd uses of
strncmp()?
--
Kees Cook
next prev parent reply other threads:[~2019-11-30 17:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 4:39 Contributing to KSPP newbie Kassad
2019-11-29 11:29 ` Mark Rutland
2019-11-29 17:32 ` Kassad
2019-11-30 17:11 ` Kees Cook [this message]
2019-11-30 16:48 ` Kees Cook
2019-11-30 16:54 ` Kees Cook
2019-12-02 10:47 ` Mark Rutland
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=201911300855.BC12761@keescook \
--to=keescook@chromium.org \
--cc=aashad940@gmail.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=mark.rutland@arm.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.