diff options
| author | Stefan Agner <stefan.agner@toradex.com> | 2016-09-16 13:17:18 -0700 |
|---|---|---|
| committer | Stefan Agner <stefan.agner@toradex.com> | 2016-09-29 13:58:03 -0700 |
| commit | cd89f007101ad44dc318b2aca826b5754c5ccfa9 (patch) | |
| tree | 75cddcca3c07f8c06e053398eeb618f3da458169 /Documentation/module-signing.txt | |
| parent | 45de59e3f1511606433c294e9ec85c5b9d4f637f (diff) | |
| parent | 1d074db69c46d62ce82b331c2080e2fcb710bf4a (diff) | |
Merge tag 'v4.4.21' into toradex_vf_4.4-next
This is the 4.4.21 stable release
Diffstat (limited to 'Documentation/module-signing.txt')
| -rw-r--r-- | Documentation/module-signing.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/module-signing.txt b/Documentation/module-signing.txt index a78bf1ffa68c..39b7f612c418 100644 --- a/Documentation/module-signing.txt +++ b/Documentation/module-signing.txt @@ -271,3 +271,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. |