summaryrefslogtreecommitdiffstats
path: root/samples/kobject
diff options
context:
space:
mode:
authorKonstantin Ryabitsev <konstantin@linuxfoundation.org>2018-02-01 15:42:33 +0100
committerJonathan Corbet <corbet@lwn.net>2018-02-01 18:58:19 +0100
commitb72dde3869fbac36aa95e50fbff4ff006a5125dd (patch)
treec5a33b9c2bae512346f7ef2cd477548f4dcc4c8d /samples/kobject
parentMerge tag 'docs-4.16' of git://git.lwn.net/linux (diff)
downloadlinux-b72dde3869fbac36aa95e50fbff4ff006a5125dd.tar.xz
linux-b72dde3869fbac36aa95e50fbff4ff006a5125dd.zip
Documentation/process: kernel maintainer PGP guide
This guide is an adapted version of the more general "Protecting Code Integrity" guide written and maintained by The Linux Foundation IT for use with open-source projects. It provides the oft-lacking guidance on the following topics: - how to properly protect one's PGP keys to minimize the risks of them being stolen and used maliciously to impersonate a kernel developer - how to configure Git to properly use GnuPG - when and how to use PGP with Git - how to verify fellow Linux Kernel developer identities I believe this document should live with the rest of the documentation describing proper processes one should follow when participating in kernel development. Placing it in a wiki on some place like kernel.org would be insufficient for a number of reasons -- primarily, because only a relatively small subset of maintainers have accounts on kernel.org, but also because even those who do rarely remember that such wiki exists. Keeping it with the rest of in-kernel docs should hopefully give it more visibility, but also help keep it up-to-date as tools and processes evolve. Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'samples/kobject')
0 files changed, 0 insertions, 0 deletions