On 11/5/18 1:38 AM, Anuj Mittal wrote:
Hi Bruce,

This change adds features to enable module signing [1] when included.

CONFIG_MODULE_SIG_FORCE is included in a seprate force-signing.scc to be
used by BSPs that would want all modules to be validly signed and reject
the ones not signed or not signed using a valid key.

Please merge in 4.14 and beyond if this looks okay.

Looks fine to me. No concerns here.

   4c4a0c67fd78..dac0479ff81a  master -> master
   89791174e7f6..0f839b780ed3  yocto-4.14 -> yocto-4.14
   a28fd4843381..ed1978c99214  yocto-4.18 -> yocto-4.18
   f32f48feff9b..86fdeb05f63e  yocto-4.19 -> yocto-4.19



[1] https://www.kernel.org/doc/Documentation/admin-guide/module-signing.rst

Anuj Mittal (1):
   features/module-signing: add new feature

  features/module-signing/force-signing.cfg | 1 +
  features/module-signing/force-signing.scc | 6 ++++++
  features/module-signing/signing.cfg       | 4 ++++
  features/module-signing/signing.scc       | 4 ++++
  4 files changed, 15 insertions(+)
  create mode 100644 features/module-signing/force-signing.cfg
  create mode 100644 features/module-signing/force-signing.scc
  create mode 100644 features/module-signing/signing.cfg
  create mode 100644 features/module-signing/signing.scc


--
_______________________________________________
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Reply via email to