Lines Matching full:developers
9 This document is aimed at Linux kernel developers, and especially at
22 communication channels between developers via PGP-signed email exchange.
30 developers who create official kernel releases. These signatures offer a
32 kernel.org or any other mirrors are identical to what these developers
40 Trusting the developers, not infrastructure
47 that trust must always be placed with developers and never with the code
52 want to make sure that by placing trust into developers we do not simply
54 The goal is to provide a set of guidelines developers can use to create
212 The more signatures you have on your PGP key from other developers, the
426 …r a free Nitrokey Start`: https://www.kernel.org/nitrokey-digital-tokens-for-kernel-developers.html
690 developers to ensure that the git repository they are pulling from has
736 this reason, most kernel developers don't bother signing their commits
743 upstream developers do not directly benefit from this practice.
846 developers' public keys, then you can jumpstart your keyring by relying
865 Kernel.org publishes the WKD for all developers who have kernel.org
873 UID to your key`_ to make WKD more useful to other kernel developers.
909 Kernel.org maintains a git repository with developers' public keys as a