linux-dev/Documentation/module-signing.txt, branch linus/master

Documentation/module-signing.txt: convert to ReST markup

2016-10-24T10:12:35Z

- Fix identatio for the document title; - remove its index; - create a table for hash algorithm to be used; - use quote blocks where needed; - use monotonic fonts for parameters; - adjust whitespaces and blank lines; - Fix case on section titles; - add it to the user's book. Signed-off-by: Mauro Carvalho Chehab

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

2016-07-27T03:08:00Z

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: Ben Hutchings Cc: stable@vger.kernel.org Signed-off-by: Rusty Russell

modsign: Fix documentation on module signing enforcement parameter.

2016-03-12T08:48:11Z

Modify the documentation to match the actual parameter as implemented in kernel/module.c:273. Signed-off-by: James Johnston Reviewed-by: David Howells Signed-off-by: Jonathan Corbet

Move certificate handling to its own directory

2015-08-14T15:06:13Z

Move certificate handling out of the kernel/ directory and into a certs/ directory to get all the weird stuff in one place and move the generated signing keys into this directory. Signed-off-by: David Howells Reviewed-by: David Woodhouse

sign-file: Document dependency on OpenSSL devel libraries

2015-08-12T16:01:01Z

The revised sign-file program is no longer a script that wraps the openssl program, but now rather a program that makes use of OpenSSL's crypto library. This means that to build the sign-file program, the kernel build process now has a dependency on the OpenSSL development packages in addition to OpenSSL itself. Document this in Kconfig and in module-signing.txt. Signed-off-by: David Howells Reviewed-by: David Woodhouse

modsign: Add explicit CONFIG_SYSTEM_TRUSTED_KEYS option

2015-08-07T15:26:14Z

Let the user explicitly provide a file containing trusted keys, instead of just automatically finding files matching *.x509 in the build tree and trusting whatever we find. This really ought to be an *explicit* configuration, and the build rules for dealing with the files were fairly painful too. Fix applied from James Morris that removes an '=' from a macro definition in kernel/Makefile as this is a feature that only exists from GNU make 3.82 onwards. Signed-off-by: David Woodhouse Signed-off-by: David Howells

modsign: Use single PEM file for autogenerated key

2015-08-07T15:26:14Z

The current rule for generating signing_key.priv and signing_key.x509 is a classic example of a bad rule which has a tendency to break parallel make. When invoked to create *either* target, it generates the other target as a side-effect that make didn't predict. So let's switch to using a single file signing_key.pem which contains both key and certificate. That matches what we do in the case of an external key specified by CONFIG_MODULE_SIG_KEY anyway, so it's also slightly cleaner. Signed-off-by: David Woodhouse Signed-off-by: David Howells

modsign: Extract signing cert from CONFIG_MODULE_SIG_KEY if needed

2015-08-07T15:26:14Z

Where an external PEM file or PKCS#11 URI is given, we can get the cert from it for ourselves instead of making the user drop signing_key.x509 in place for us. Signed-off-by: David Woodhouse Signed-off-by: David Howells

modsign: Allow external signing key to be specified

2015-08-07T15:26:14Z

Signed-off-by: David Woodhouse Signed-off-by: David Howells

modsign: Allow password to be specified for signing key

2015-08-07T15:26:14Z

We don't want this in the Kconfig since it might then get exposed in /proc/config.gz. So make it a parameter to Kbuild instead. This also means we don't have to jump through hoops to strip quotes from it, as we would if it was a config option. Signed-off-by: David Woodhouse Signed-off-by: David Howells Reviewed-by: Mimi Zohar