| title |
|---|
Get Involved |
- TOC {:toc}
Want to get involved in the Kernel Self Protection Project? Here's how:
- Subscribe to the upstream Linux kernel hardening mailing list,
[email protected], where development, maintenance, and administrivia happen. (And visit the list archive.) - Come to the every-2-weeks status update meeting. See the calendar for details.
- Join the
#linux-hardeningIRC channel on Libera.Chat. - Optionally subscribe to the general kernel hardening mailing list,
[email protected], where new hardening topics for any kind of system (not just Linux) get discussed. (And visit the list archive.)- Note: when sending to
[email protected], please also CC[email protected]too.
- Note: when sending to
Send an email to the lists to introduce yourself!
- What topics are you interested in?
- What do you want to learn about?
- What experience do you have with security, the kernel, programming, or anything else you think is important.
Pick something from the issue tracker (or add a new one), coordinate on the mailing lists, and get started. If your employer is brave enough to understand how critical this work is, they'll pay you to work on it. If not, the OpenSSF's Alpha-Omega group is in a great position to fund specific work proposals. We need kernel developers, compiler developers, testers, backporters, a documentation writers.
Please send new topics and patch series to [email protected].
When contributing patches for the Linux kernel, be sure to follow the Linux kernel Coding Style Guide and read about Submitting Patches.
Even if you're only sending your patches to the mailing lists for some early review, it's best to get as much of the coding style and submission semantics correct to avoid reviewers needing to recommend changes in those areas.