1. 04 1月, 2016 1 次提交
  2. 28 12月, 2015 1 次提交
  3. 21 12月, 2015 1 次提交
  4. 14 12月, 2015 1 次提交
  5. 07 12月, 2015 1 次提交
  6. 30 11月, 2015 1 次提交
  7. 23 11月, 2015 1 次提交
  8. 16 11月, 2015 1 次提交
  9. 02 11月, 2015 1 次提交
  10. 25 10月, 2015 1 次提交
  11. 19 10月, 2015 1 次提交
  12. 12 10月, 2015 1 次提交
  13. 08 10月, 2015 1 次提交
  14. 04 10月, 2015 1 次提交
  15. 01 10月, 2015 1 次提交
  16. 28 9月, 2015 1 次提交
    • B
      DocBook: Use a fixed encoding for output · b479bfd0
      Ben Hutchings 提交于
      Currently the encoding of documents generated by DocBook depends on
      the current locale.  Make the output reproducible independently of
      the locale, by setting the encoding to UTF-8 (LC_CTYPE=C.UTF-8) by
      preference, or ASCII (LC_CTYPE=C) as a fallback.
      
      LC_CTYPE can normally be overridden by LC_ALL, but the top-level
      Makefile unsets that.
      Signed-off-by: NBen Hutchings <ben@decadent.org.uk>
      [jc: added check-lc_ctype to .gitignore]
      Signed-off-by: NJonathan Corbet <corbet@lwn.net>
      b479bfd0
  17. 27 9月, 2015 1 次提交
  18. 21 9月, 2015 1 次提交
  19. 13 9月, 2015 1 次提交
  20. 04 9月, 2015 1 次提交
  21. 31 8月, 2015 1 次提交
  22. 28 8月, 2015 1 次提交
  23. 24 8月, 2015 1 次提交
  24. 17 8月, 2015 1 次提交
  25. 14 8月, 2015 2 次提交
  26. 10 8月, 2015 1 次提交
  27. 07 8月, 2015 3 次提交
    • D
      modsign: Use single PEM file for autogenerated key · fb117949
      David Woodhouse 提交于
      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: NDavid Woodhouse <David.Woodhouse@intel.com>
      Signed-off-by: NDavid Howells <dhowells@redhat.com>
      fb117949
    • D
    • D
      MODSIGN: Use PKCS#7 messages as module signatures · 3f1e1bea
      David Howells 提交于
      Move to using PKCS#7 messages as module signatures because:
      
       (1) We have to be able to support the use of X.509 certificates that don't
           have a subjKeyId set.  We're currently relying on this to look up the
           X.509 certificate in the trusted keyring list.
      
       (2) PKCS#7 message signed information blocks have a field that supplies the
           data required to match with the X.509 certificate that signed it.
      
       (3) The PKCS#7 certificate carries fields that specify the digest algorithm
           used to generate the signature in a standardised way and the X.509
           certificates specify the public key algorithm in a standardised way - so
           we don't need our own methods of specifying these.
      
       (4) We now have PKCS#7 message support in the kernel for signed kexec purposes
           and we can make use of this.
      
      To make this work, the old sign-file script has been replaced with a program
      that needs compiling in a previous patch.  The rules to build it are added
      here.
      Signed-off-by: NDavid Howells <dhowells@redhat.com>
      Tested-by: NVivek Goyal <vgoyal@redhat.com>
      3f1e1bea
  28. 03 8月, 2015 1 次提交
  29. 27 7月, 2015 1 次提交
  30. 22 7月, 2015 2 次提交
  31. 20 7月, 2015 1 次提交
  32. 13 7月, 2015 1 次提交
  33. 06 7月, 2015 2 次提交
  34. 22 6月, 2015 1 次提交
  35. 15 6月, 2015 1 次提交