From: Kees Cook <keescook@chromium.org>
To: Oscar Carter <oscar.carter@gmx.com>
Cc: kernel-hardening@lists.openwall.com
Subject: Re: Get involved in the KSPP
Date: Mon, 11 May 2020 09:15:18 -0700 [thread overview]
Message-ID: <202005110912.3A26AF11@keescook> (raw)
In-Reply-To: <20200509122007.GA5356@ubuntu>
On Sat, May 09, 2020 at 02:20:08PM +0200, Oscar Carter wrote:
> Hi, my name is Oscar. I would like to get involved in the kernel self protection
> project because I love the software security and I think this is one of the most
> challenging fields.
Hi Oscar! Welcome to the mailing list. :)
> I have experience in microcrontrollers and working with low level software, but
> my experience with the linux kernel development is a few commits in the staging
> area.
>
> For now, and due to my low experience with the linux kernel code and software
> security, I do not care about the area and task to be done. What I pretend is to
> help this great community and improve my knowledge and skills in this
> challenging field.
>
> So, I would like to know if I can be assigned to some task that suits me. I've
> taken a look at https://github.com/KSPP/linux/issues but I don't know which task
> to choose and if someone else is working on it.
There's "good first issue" label that might help you choose things:
https://github.com/KSPP/linux/labels/good%20first%20issue
One mostly mechanical bit of work would be this:
https://github.com/KSPP/linux/issues/20
There are likely more fixes needed to build the kernel with
-Wcast-function-type (especially on non-x86 kernels). So that would let
you learn about cross-compiling, etc.
Let us know what you think!
Take care,
--
Kees Cook
next prev parent reply other threads:[~2020-05-11 16:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 12:20 Get involved in the KSPP Oscar Carter
2020-05-11 16:15 ` Kees Cook [this message]
2020-05-14 17:20 ` Oscar Carter
2020-05-15 8:27 ` Kees Cook
2020-05-16 7:25 ` Oscar Carter
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=202005110912.3A26AF11@keescook \
--to=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=oscar.carter@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).