Skip to content
Snippets Groups Projects
  1. Feb 29, 2016
  2. Feb 26, 2016
    • Mehmet Kayaalp's avatar
      KEYS: Reserve an extra certificate symbol for inserting without recompiling · c4c36105
      Mehmet Kayaalp authored
      
      Place a system_extra_cert buffer of configurable size, right after the
      system_certificate_list, so that inserted keys can be readily processed by
      the existing mechanism. Added script takes a key file and a kernel image
      and inserts its contents to the reserved area. The
      system_certificate_list_size is also adjusted accordingly.
      
      Call the script as:
      
          scripts/insert-sys-cert -b <vmlinux> -c <certfile>
      
      If vmlinux has no symbol table, supply System.map file with -s flag.
      Subsequent runs replace the previously inserted key, instead of appending
      the new one.
      
      Signed-off-by: default avatarMehmet Kayaalp <mkayaalp@linux.vnet.ibm.com>
      Signed-off-by: default avatarDavid Howells <dhowells@redhat.com>
      Acked-by: default avatarMimi Zohar <zohar@linux.vnet.ibm.com>
      c4c36105
    • Arnd Bergmann's avatar
      modsign: hide openssl output in silent builds · 5d06ee20
      Arnd Bergmann authored
      
      When a user calls 'make -s', we can assume they don't want to
      see any output except for warnings and errors, but instead
      they see this for a warning free build:
      
       ###
       ### Now generating an X.509 key pair to be used for signing modules.
       ###
       ### If this takes a long time, you might wish to run rngd in the
       ### background to keep the supply of entropy topped up.  It
       ### needs to be run as root, and uses a hardware random
       ### number generator if one is available.
       ###
       Generating a 4096 bit RSA private key
       .................................................................................................................................................................................................................................++
       ..............................................................................................................................++
       writing new private key to 'certs/signing_key.pem'
       -----
       ###
       ### Key pair generated.
       ###
      
      The output can confuse simple build testing scripts that just check
      for an empty build log.
      
      This patch silences all the output:
       - "echo" is changed to "@$(kecho)", which is dropped when "-s" gets
         passed
       - the openssl command itself is only printed with V=1, using the
         $(Q) macro
       - The output of openssl gets redirected to /dev/null on "-s" builds.
      
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarDavid Howells <dhowells@redhat.com>
      5d06ee20
  3. Feb 09, 2016
  4. Oct 21, 2015
  5. Aug 14, 2015
    • David Woodhouse's avatar
      modsign: Handle signing key in source tree · 3ee550f1
      David Woodhouse authored
      
      Since commit 1329e8cc ("modsign: Extract signing cert from
      CONFIG_MODULE_SIG_KEY if needed"), the build system has carefully coped
      with the signing key being specified as a relative path in either the
      source or or the build trees.
      
      However, the actual signing of modules has not worked if the filename
      is relative to the source tree.
      
      Fix that by moving the config_filename helper into scripts/Kbuild.include
      so that it can be used from elsewhere, and then using it in the top-level
      Makefile to find the signing key file.
      
      Kill the intermediate $(MODPUBKEY) and $(MODSECKEY) variables too, while
      we're at it. There's no need for them.
      
      Signed-off-by: default avatarDavid Woodhouse <David.Woodhouse@intel.com>
      Signed-off-by: default avatarDavid Howells <dhowells@redhat.com>
      3ee550f1
    • David Woodhouse's avatar
      modsign: Use if_changed rule for extracting cert from module signing key · 62172c81
      David Woodhouse authored
      
      We couldn't use if_changed for this before, because it didn't live in
      the kernel/ directory so we couldn't add it to $(targets). It was easier
      just to leave it as it was.
      
      Now it's in the certs/ directory we can use if_changed, the same as we
      do for the trusted certificate list.
      
      Aside from making things consistent, this means we don't need to depend
      explicitly on the include/config/module/sig/key.h file. And we also get
      to automatically do the right thing and re-extract the cert if the user
      does odd things like using a relative filename and then playing silly
      buggers with adding/removing that file in both the source and object
      trees. We always favour the one in the object tree if it exists, and
      now we'll correctly re-extract the cert when it changes. Previously we'd
      *only* re-extract the cert if the config option changed, even if the
      actual file we're using did change.
      
      Signed-off-by: default avatarDavid Woodhouse <David.Woodhouse@intel.com>
      Signed-off-by: default avatarDavid Howells <dhowells@redhat.com>
      62172c81
    • David Howells's avatar
      Move certificate handling to its own directory · cfc411e7
      David Howells authored
      
      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: default avatarDavid Howells <dhowells@redhat.com>
      Reviewed-by: default avatarDavid Woodhouse <David.Woodhouse@intel.com>
      cfc411e7
Loading