Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 5a7dd70c authored by Ben Hutchings's avatar Ben Hutchings Committed by Sasha Levin
Browse files

Documentation/module-signing.txt: Note need for version info if reusing a key 



[ Upstream commit b8612e517c3c9809e1200b72c474dbfd969e5a83 ]

Signing a module should only make it trusted by the specific kernel it
was built for, not anything else.  If a module signing key is used for
multiple ABI-incompatible kernels, the modules need to include enough
version information to distinguish them.

Signed-off-by: default avatarBen Hutchings <ben@decadent.org.uk>
Cc: stable@vger.kernel.org
Signed-off-by: default avatarRusty Russell <rusty@rustcorp.com.au>
Signed-off-by: default avatarSasha Levin <alexander.levin@verizon.com>
parent 1d307756

Documentation/module-signing.txt

+6 −0
Original line number Diff line number Diff line
@@ -239,3 +239,9 @@ Since the private key is used to sign modules, viruses and malware could use 
the private key to sign modules and compromise the operating system.  The

private key must be either destroyed or moved to a secure location and not kept

in the root node of the kernel source tree.



If you use the same private key to sign modules for multiple kernel

configurations, you must ensure that the module version information is

sufficient to prevent loading a module into a different kernel.  Either

set CONFIG_MODVERSIONS=y or ensure that each configuration has a different

kernel release string by changing EXTRAVERSION or CONFIG_LOCALVERSION.