Kernel Self Protection Project/Get Involved - Revision history

KeesCook: add TZ to calendar link

2023-02-10T00:31:25Z

add TZ to calendar link

← Older revision		Revision as of 00:31, 10 February 2023
Line 4:		Line 4:

	* Subscribe to the [http://vger.kernel.org/vger-lists.html#linux-hardening '''upstream''' Linux kernel hardening mailing list], <code>'''linux'''-hardening@vger.kernel.org</code>, where development, maintenance, and administrivia happen. (And visit the [https://lore.kernel.org/linux-hardening/ list archive].)		* Subscribe to the [http://vger.kernel.org/vger-lists.html#linux-hardening '''upstream''' Linux kernel hardening mailing list], <code>'''linux'''-hardening@vger.kernel.org</code>, where development, maintenance, and administrivia happen. (And visit the [https://lore.kernel.org/linux-hardening/ list archive].)
	* Come to the every-2-weeks status update meeting. See the [https://calendar.google.com/calendar/embed?src=47005f8f50f21da6133d7239f3cb93d1624d2e1949963ea75dd86d5f2d5721e0~~%40group~~.calendar.google.com calendar] for details.		* Come to the every-2-weeks status update meeting. See the [https://calendar.google.com/calendar/u/0/embed?src=47005f8f50f21da6133d7239f3cb93d1624d2e1949963ea75dd86d5f2d5721e0@group.calendar.google.com&ctz=America/Los_Angeles calendar] for details.
	* Join the <code>#linux-hardening</code> IRC channel on [https://libera.chat/ Libera.Chat].		* Join the <code>#linux-hardening</code> IRC channel on [https://libera.chat/ Libera.Chat].
	* Optionally subscribe to the [https://www.openwall.com/lists/kernel-hardening/ '''general''' Linux kernel hardening mailing list], <code>'''kernel'''-hardening@lists.openwall.com</code>, where new hardening topics and summaries of completed work are discussed. (And visit the [https://lore.kernel.org/kernel-hardening/ list archive].)		* Optionally subscribe to the [https://www.openwall.com/lists/kernel-hardening/ '''general''' Linux kernel hardening mailing list], <code>'''kernel'''-hardening@lists.openwall.com</code>, where new hardening topics and summaries of completed work are discussed. (And visit the [https://lore.kernel.org/kernel-hardening/ list archive].)

KeesCook at 19:46, 25 January 2023

2023-01-25T19:46:30Z

← Older revision		Revision as of 19:46, 25 January 2023
Line 4:		Line 4:

	* Subscribe to the [http://vger.kernel.org/vger-lists.html#linux-hardening '''upstream''' Linux kernel hardening mailing list], <code>'''linux'''-hardening@vger.kernel.org</code>, where development, maintenance, and administrivia happen. (And visit the [https://lore.kernel.org/linux-hardening/ list archive].)		* Subscribe to the [http://vger.kernel.org/vger-lists.html#linux-hardening '''upstream''' Linux kernel hardening mailing list], <code>'''linux'''-hardening@vger.kernel.org</code>, where development, maintenance, and administrivia happen. (And visit the [https://lore.kernel.org/linux-hardening/ list archive].)
	* ~~Subscribe~~ to the [https://www.openwall.com/lists/kernel-hardening/ '''general''' Linux kernel hardening mailing list], <code>'''kernel'''-hardening@lists.openwall.com</code>, where new hardening topics and summaries of completed work are discussed. (And visit the [https://lore.kernel.org/kernel-hardening/ list archive].)		* Come to the every-2-weeks status update meeting. See the [https://calendar.google.com/calendar/embed?src=47005f8f50f21da6133d7239f3cb93d1624d2e1949963ea75dd86d5f2d5721e0%40group.calendar.google.com calendar] for details.
			* Join the <code>#linux-hardening</code> IRC channel on [https://libera.chat/ Libera.Chat].
			* Optionally subscribe to the [https://www.openwall.com/lists/kernel-hardening/ '''general''' Linux kernel hardening mailing list], <code>'''kernel'''-hardening@lists.openwall.com</code>, where new hardening topics and summaries of completed work are discussed. (And visit the [https://lore.kernel.org/kernel-hardening/ list archive].)
	** Note: when sending to <code>kernel-hardening@lists.openwall.com</code>, please also CC <code>linux-hardening@vger.kernel.org</code> too.		** Note: when sending to <code>kernel-hardening@lists.openwall.com</code>, please also CC <code>linux-hardening@vger.kernel.org</code> too.
	* (Optional) Join the <code>#linux-hardening</code> IRC channel on [https://libera.chat/ Libera.Chat].
	* Come to the every-2-weeks status update meeting. See the [https://calendar.google.com/calendar/embed?src=47005f8f50f21da6133d7239f3cb93d1624d2e1949963ea75dd86d5f2d5721e0%40group.calendar.google.com calendar] for details.

	= Introduce Yourself =		= Introduce Yourself =

KeesCook: add calendar

2023-01-25T19:45:15Z

add calendar

← Older revision		Revision as of 19:45, 25 January 2023
Line 7:		Line 7:
	** Note: when sending to <code>kernel-hardening@lists.openwall.com</code>, please also CC <code>linux-hardening@vger.kernel.org</code> too.		** Note: when sending to <code>kernel-hardening@lists.openwall.com</code>, please also CC <code>linux-hardening@vger.kernel.org</code> too.
	* (Optional) Join the <code>#linux-hardening</code> IRC channel on [https://libera.chat/ Libera.Chat].		* (Optional) Join the <code>#linux-hardening</code> IRC channel on [https://libera.chat/ Libera.Chat].
			* Come to the every-2-weeks status update meeting. See the [https://calendar.google.com/calendar/embed?src=47005f8f50f21da6133d7239f3cb93d1624d2e1949963ea75dd86d5f2d5721e0%40group.calendar.google.com calendar] for details.

	= Introduce Yourself =		= Introduce Yourself =

KeesCook: ditch freenode

2021-05-27T05:35:58Z

ditch freenode

← Older revision		Revision as of 05:35, 27 May 2021
Line 6:		Line 6:
	* Subscribe to the [https://www.openwall.com/lists/kernel-hardening/ '''general''' Linux kernel hardening mailing list], <code>'''kernel'''-hardening@lists.openwall.com</code>, where new hardening topics and summaries of completed work are discussed. (And visit the [https://lore.kernel.org/kernel-hardening/ list archive].)		* Subscribe to the [https://www.openwall.com/lists/kernel-hardening/ '''general''' Linux kernel hardening mailing list], <code>'''kernel'''-hardening@lists.openwall.com</code>, where new hardening topics and summaries of completed work are discussed. (And visit the [https://lore.kernel.org/kernel-hardening/ list archive].)
	** Note: when sending to <code>kernel-hardening@lists.openwall.com</code>, please also CC <code>linux-hardening@vger.kernel.org</code> too.		** Note: when sending to <code>kernel-hardening@lists.openwall.com</code>, please also CC <code>linux-hardening@vger.kernel.org</code> too.
	* (Optional) Join the <code>##linux-~~hardened~~</code> IRC channel on [https://~~freenode~~.~~net~~/ ~~freenode~~].		* (Optional) Join the <code>#linux-hardening</code> IRC channel on [https://libera.chat/ Libera.Chat].

	= Introduce Yourself =		= Introduce Yourself =

KeesCook: /* Pick something to work on */

2020-10-18T17:23:14Z

Pick something to work on

← Older revision		Revision as of 17:23, 18 October 2020
Line 18:		Line 18:
	= Pick something to work on =		= Pick something to work on =

	Pick something from the [https://github.com/KSPP/issues 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 [https://www.linuxfoundation.org/ Linux Foundation]'s [https://www.coreinfrastructure.org/faq Core Infrastructure Initiative] is in a great position to fund specific work proposals. We need kernel developers, compiler developers, testers, backporters, a documentation writers.		Pick something from the [https://github.com/KSPP/linux/issues 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 [https://www.linuxfoundation.org/ Linux Foundation]'s [https://www.coreinfrastructure.org/faq Core Infrastructure Initiative] is in a great position to fund specific work proposals. We need kernel developers, compiler developers, testers, backporters, a documentation writers.

	= Contribute patches =		= Contribute patches =

KeesCook: moar cleanup

2020-10-05T22:22:27Z

moar cleanup

← Older revision		Revision as of 22:22, 5 October 2020
Line 3:		Line 3:
	= Join the conversations =		= Join the conversations =

	* ~~Join~~ the [http://vger.kernel.org/vger-lists.html#linux-hardening upstream Linux kernel hardening mailing list] where development, maintenance, and administrivia happen. (And visit the [https://lore.kernel.org/linux-hardening/ list archive].)		* Subscribe to the [http://vger.kernel.org/vger-lists.html#linux-hardening '''upstream''' Linux kernel hardening mailing list], <code>'''linux'''-hardening@vger.kernel.org</code>, where development, maintenance, and administrivia happen. (And visit the [https://lore.kernel.org/linux-hardening/ list archive].)
	* ~~Join~~ the [https://www.openwall.com/lists/kernel-hardening/ general Linux kernel hardening mailing list], where new hardening topics are discussed. (And visit the [https://lore.kernel.org/kernel-hardening/ list archive].)		* Subscribe to the [https://www.openwall.com/lists/kernel-hardening/ '''general''' Linux kernel hardening mailing list], <code>'''kernel'''-hardening@lists.openwall.com</code>, where new hardening topics and summaries of completed work are discussed. (And visit the [https://lore.kernel.org/kernel-hardening/ list archive].)
			** Note: when sending to <code>kernel-hardening@lists.openwall.com</code>, please also CC <code>linux-hardening@vger.kernel.org</code> too.
	* (Optional) Join the <code>##linux-hardened</code> IRC channel on [https://freenode.net/ freenode].		* (Optional) Join the <code>##linux-hardened</code> IRC channel on [https://freenode.net/ freenode].

KeesCook: more cleanup

2020-10-05T22:13:20Z

more cleanup

← Older revision		Revision as of 22:13, 5 October 2020
Line 1:		Line 1:
	Want to get involved in the [[Kernel Self Protection Project]]? Here's how:		Want to get involved in the [[Kernel Self Protection Project]]? Here's how:

			= Join the conversations =

	* Join the [http://vger.kernel.org/vger-lists.html#linux-hardening upstream Linux kernel hardening mailing list] where development, maintenance, and administrivia happen. (And visit the [https://lore.kernel.org/linux-hardening/ list archive].)		* Join the [http://vger.kernel.org/vger-lists.html#linux-hardening upstream Linux kernel hardening mailing list] where development, maintenance, and administrivia happen. (And visit the [https://lore.kernel.org/linux-hardening/ list archive].)
Line 7:		Line 9:
	= Introduce Yourself =		= Introduce Yourself =

	Send an email to introduce yourself! ~~Then pick an area of~~ work from the [https://github.com/KSPP/issues 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 [https://www.linuxfoundation.org/ Linux Foundation]'s [https://www.coreinfrastructure.org/faq Core Infrastructure Initiative] is in a great position to fund specific work proposals. We need kernel developers, compiler developers, testers, backporters, a documentation writers.		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 to work on =

			Pick something from the [https://github.com/KSPP/issues 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 [https://www.linuxfoundation.org/ Linux Foundation]'s [https://www.coreinfrastructure.org/faq Core Infrastructure Initiative] is in a great position to fund specific work proposals. We need kernel developers, compiler developers, testers, backporters, a documentation writers.

	= ~~Patch Contribution Guidelines~~ =		= Contribute patches =

	Please send new topics and patch series to both [http://vger.kernel.org/vger-lists.html#linux-hardening linux-hardening@vger.kernel.org] and [https://www.openwall.com/lists/kernel-hardening kernel-hardening@lists.openwall.com] for the widest audience possible.		Please send new topics and patch series to both [http://vger.kernel.org/vger-lists.html#linux-hardening linux-hardening@vger.kernel.org] and [https://www.openwall.com/lists/kernel-hardening kernel-hardening@lists.openwall.com] for the widest audience possible.

KeesCook at 22:09, 5 October 2020

2020-10-05T22:09:24Z

← Older revision		Revision as of 22:09, 5 October 2020
Line 1:		Line 1:
	Want to get involved in the [[Kernel Self Protection Project]]? Here's how:		Want to get involved in the [[Kernel Self Protection Project]]? Here's how:

	- Join the [http://vger.kernel.org/vger-lists.html#linux-hardening upstream Linux kernel hardening mailing list] where development, maintenance, and administrivia happen. (And visit the [https://lore.kernel.org/linux-hardening/ list archive].)		* Join the [http://vger.kernel.org/vger-lists.html#linux-hardening upstream Linux kernel hardening mailing list] where development, maintenance, and administrivia happen. (And visit the [https://lore.kernel.org/linux-hardening/ list archive].)
	- Join the [https://www.openwall.com/lists/kernel-hardening/ general Linux kernel hardening mailing list], where new hardening topics are discussed. (And visit the [https://lore.kernel.org/kernel-hardening/ list archive].)		* Join the [https://www.openwall.com/lists/kernel-hardening/ general Linux kernel hardening mailing list], where new hardening topics are discussed. (And visit the [https://lore.kernel.org/kernel-hardening/ list archive].)
	- (Optional) Join the <code>##linux-hardened</code> IRC channel on [https://freenode.net/ freenode].		* (Optional) Join the <code>##linux-hardened</code> IRC channel on [https://freenode.net/ freenode].

	= Introduce Yourself =		= Introduce Yourself =

KeesCook: update list descriptions, tweak capitalization, and split up contribution guildeline better

2020-10-05T22:08:46Z

update list descriptions, tweak capitalization, and split up contribution guildeline better

← Older revision		Revision as of 22:08, 5 October 2020
Line 1:		Line 1:
	Want to get involved in the [[Kernel Self Protection Project]]? [http://vger.kernel.org/vger-lists.html#linux-hardening ~~Join~~] the [https://lore.kernel.org/linux-hardening/ Linux kernel hardening mailing list], ~~or hop on IRC at~~ <code>##linux-hardened</code> on [https://freenode.net/ freenode]~~. You may also want to join the general [https://www.openwall.com/lists/kernel-hardening/ kernel hardening list] too, where new topics are frequently discussed~~.		Want to get involved in the [[Kernel Self Protection Project]]? Here's how:

			- Join the [http://vger.kernel.org/vger-lists.html#linux-hardening upstream Linux kernel hardening mailing list] where development, maintenance, and administrivia happen. (And visit the [https://lore.kernel.org/linux-hardening/ list archive].)
			- Join the [https://www.openwall.com/lists/kernel-hardening/ general Linux kernel hardening mailing list], where new hardening topics are discussed. (And visit the [https://lore.kernel.org/kernel-hardening/ list archive].)
			- (Optional) Join the <code>##linux-hardened</code> IRC channel on [https://freenode.net/ freenode].

	= Introduce Yourself =		= Introduce Yourself =

	Send an email to introduce yourself! Then pick an area of work from ~~below (~~or add a new one), coordinate on the mailing ~~list~~, 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 [https://www.linuxfoundation.org/ Linux Foundation]'s [https://www.coreinfrastructure.org/faq Core Infrastructure Initiative] is in a great position to fund specific work proposals. We need kernel developers, compiler developers, testers, backporters, a documentation writers.		Send an email to introduce yourself! Then pick an area of work from the [https://github.com/KSPP/issues 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 [https://www.linuxfoundation.org/ Linux Foundation]'s [https://www.coreinfrastructure.org/faq Core Infrastructure Initiative] is in a great position to fund specific work proposals. We need kernel developers, compiler developers, testers, backporters, a documentation writers.

	= Patch Contribution Guidelines =		= Patch Contribution Guidelines =

	When contributing patches for the Linux kernel, be sure to follow the Linux kernel [https://www.kernel.org/doc/html/latest/process/coding-style.html Coding Style Guide] and read about [https://www.kernel.org/doc/html/latest/process/submitting-patches.html Submitting Patches]. Even if you're only sending your patches to the ~~kernel-hardening~~ mailing ~~list~~ 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.		Please send new topics and patch series to both [http://vger.kernel.org/vger-lists.html#linux-hardening linux-hardening@vger.kernel.org] and [https://www.openwall.com/lists/kernel-hardening kernel-hardening@lists.openwall.com] for the widest audience possible.

			When contributing patches for the Linux kernel, be sure to follow the Linux kernel [https://www.kernel.org/doc/html/latest/process/coding-style.html Coding Style Guide] and read about [https://www.kernel.org/doc/html/latest/process/submitting-patches.html 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.

			== grsecurity and other non-upstream patch sources ==

	As with any other ~~Open Source~~ project, it is particularly important that if you're working on upstreaming work from other ~~Open Source~~ projects, be sure your patches are giving credit to the original authors, that licenses are compatible, and that copyright notices are retained, etc.		As with any other Free Software project, it is particularly important that if you're working on upstreaming work from other projects, be sure your patches are giving credit to the original authors, that licenses are compatible, and that copyright notices are retained, etc.

	In the case of new files, or other places where a copyright notice would be expected to be added, be sure to retain all copyright notices from the other project. This may require some examination of commit history. For example, [https://github.com/linux-scraping/linux-grsecurity/blob/grsec-test/grsecurity/Makefile#L3 ~~Grsecurity~~'s copyright notice from their most recent public patch] does not include PaX Team's copyright notice, which is only listed in the patch for GCC plugins. For ~~Grsecurity~~ copyright, when more specific details are not easy to find, the following could be used:		In the case of new files, or other places where a copyright notice would be expected to be added, be sure to retain all copyright notices from the other project. This may require some examination of commit history. For example, [https://github.com/linux-scraping/linux-grsecurity/blob/grsec-test/grsecurity/Makefile#L3 grsecurity's copyright notice from their most recent public patch] does not include PaX Team's copyright notice, which is only listed in the patch for GCC plugins. For grsecurity copyright, when more specific details are not easy to find, the following could be used:

	Copyright (C) 2001-2017 PaX Team, Bradley Spengler, Open Source Security Inc.		Copyright (C) 2001-2017 PaX Team, Bradley Spengler, Open Source Security Inc.

	Additionally, ~~Grsecurity~~ has asked that contributors include this in commit messages for non-trivial code ported from ~~Grsecurity~~:		Additionally, grsecurity has asked that contributors include this in commit messages for non-trivial code ported from grsecurity:

	$CODE is {verbatim,modified} from Brad Spengler/PaX Team's code in the last		$CODE is {verbatim,modified} from Brad Spengler/PaX Team's code in the last

KeesCook: update mailing list

2020-09-29T17:18:04Z

update mailing list

← Older revision		Revision as of 17:18, 29 September 2020
Line 1:		Line 1:
	Want to get involved in the [[Kernel Self Protection Project]]? [http://~~www~~.~~openwall~~.~~com~~/lists/#~~subscribe~~ Join] the [~~http~~://~~www~~.~~openwall~~.~~com~~/~~lists/kernel~~-hardening/ kernel hardening mailing list], or hop on IRC at <code>##linux-hardened</code> on [https://freenode.net/ freenode].		Want to get involved in the [[Kernel Self Protection Project]]? [http://vger.kernel.org/vger-lists.html#linux-hardening Join] the [https://lore.kernel.org/linux-hardening/ Linux kernel hardening mailing list], or hop on IRC at <code>##linux-hardened</code> on [https://freenode.net/ freenode]. You may also want to join the general [https://www.openwall.com/lists/kernel-hardening/ kernel hardening list] too, where new topics are frequently discussed.

	= Introduce Yourself =		= Introduce Yourself =

	Send an email to introduce yourself! Then pick an area of work from below (or add a new one), coordinate on the mailing list, 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 [~~http~~://www.linuxfoundation.org/ Linux Foundation]'s [https://www.coreinfrastructure.org/faq Core Infrastructure Initiative] is in a great position to fund specific work proposals. We need kernel developers, compiler developers, testers, backporters, a documentation writers.		Send an email to introduce yourself! Then pick an area of work from below (or add a new one), coordinate on the mailing list, 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 [https://www.linuxfoundation.org/ Linux Foundation]'s [https://www.coreinfrastructure.org/faq Core Infrastructure Initiative] is in a great position to fund specific work proposals. We need kernel developers, compiler developers, testers, backporters, a documentation writers.

	= Patch Contribution Guidelines =		= Patch Contribution Guidelines =