1. 10 2月, 2023 1 次提交
  2. 01 7月, 2022 1 次提交
  3. 02 9月, 2021 1 次提交
  4. 10 8月, 2021 1 次提交
  5. 17 3月, 2020 1 次提交
  6. 27 2月, 2020 1 次提交
  7. 12 2月, 2020 1 次提交
  8. 15 1月, 2020 1 次提交
  9. 02 1月, 2020 1 次提交
  10. 16 10月, 2019 1 次提交
  11. 28 9月, 2019 2 次提交
    • D
      Reorganize local header files · b5acbf91
      Dr. Matthias St. Pierre 提交于
      Apart from public and internal header files, there is a third type called
      local header files, which are located next to source files in the source
      directory. Currently, they have different suffixes like
      
        '*_lcl.h', '*_local.h', or '*_int.h'
      
      This commit changes the different suffixes to '*_local.h' uniformly.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/9681)
      b5acbf91
    • D
      Reorganize private crypto header files · 0c994d54
      Dr. Matthias St. Pierre 提交于
      Currently, there are two different directories which contain internal
      header files of libcrypto which are meant to be shared internally:
      
      While header files in 'include/internal' are intended to be shared
      between libcrypto and libssl, the files in 'crypto/include/internal'
      are intended to be shared inside libcrypto only.
      
      To make things complicated, the include search path is set up in such
      a way that the directive #include "internal/file.h" could refer to
      a file in either of these two directoroes. This makes it necessary
      in some cases to add a '_int.h' suffix to some files to resolve this
      ambiguity:
      
        #include "internal/file.h"      # located in 'include/internal'
        #include "internal/file_int.h"  # located in 'crypto/include/internal'
      
      This commit moves the private crypto headers from
      
        'crypto/include/internal'  to  'include/crypto'
      
      As a result, the include directives become unambiguous
      
        #include "internal/file.h"       # located in 'include/internal'
        #include "crypto/file.h"         # located in 'include/crypto'
      
      hence the superfluous '_int.h' suffixes can be stripped.
      
      The files 'store_int.h' and 'store.h' need to be treated specially;
      they are joined into a single file.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/9681)
      0c994d54
  12. 10 9月, 2019 1 次提交
  13. 06 9月, 2019 1 次提交
  14. 14 8月, 2019 1 次提交
  15. 01 8月, 2019 1 次提交
  16. 02 7月, 2019 1 次提交
  17. 26 2月, 2019 1 次提交
  18. 08 2月, 2019 1 次提交
    • T
      Fix d2i_PublicKey() for EC keys · 3dbec21b
      Todd Short 提交于
      o2i_ECPublicKey() requires an EC_KEY structure filled with an EC_GROUP.
      
      o2i_ECPublicKey() is called by d2i_PublicKey(). In order to fulfill the
      o2i_ECPublicKey()'s requirement, d2i_PublicKey() needs to be called with
      an EVP_PKEY with an EC_KEY containing an EC_GROUP.
      
      However, the call to EVP_PKEY_set_type() frees any existing key structure
      inside the EVP_PKEY, thus freeing the EC_KEY with the EC_GROUP that
      o2i_ECPublicKey() needs.
      
      This means you can't d2i_PublicKey() for an EC key...
      
      The fix is to check to see if the type is already set appropriately, and
      if so, not call EVP_PKEY_set_type().
      Reviewed-by: NPaul Yang <yang.yang@baishancloud.com>
      Reviewed-by: NMatt Caswell <matt@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/8168)
      
      (cherry picked from commit 2aa2beb06cc25c1f8accdc3d87b946205becfd86)
      3dbec21b
  19. 08 1月, 2019 1 次提交
  20. 03 1月, 2019 1 次提交
  21. 23 12月, 2018 1 次提交
  22. 07 12月, 2018 1 次提交
  23. 09 9月, 2018 1 次提交
  24. 23 8月, 2018 1 次提交
  25. 11 8月, 2018 1 次提交
  26. 07 8月, 2018 2 次提交
  27. 01 8月, 2018 1 次提交
  28. 20 6月, 2018 1 次提交
  29. 19 6月, 2018 1 次提交
  30. 18 6月, 2018 1 次提交
  31. 08 6月, 2018 1 次提交
  32. 23 5月, 2018 1 次提交
    • V
      Limit scope of CN name constraints · d02d80b2
      Viktor Dukhovni 提交于
      Don't apply DNS name constraints to the subject CN when there's a
      least one DNS-ID subjectAlternativeName.
      
      Don't apply DNS name constraints to subject CN's that are sufficiently
      unlike DNS names.  Checked name must have at least two labels, with
      all labels non-empty, no trailing '.' and all hyphens must be
      internal in each label.  In addition to the usual LDH characters,
      we also allow "_", since some sites use these for hostnames despite
      all the standards.
      Reviewed-by: NMatt Caswell <matt@openssl.org>
      Reviewed-by: NTim Hudson <tjh@openssl.org>
      d02d80b2
  33. 03 5月, 2018 1 次提交
  34. 01 5月, 2018 1 次提交
  35. 24 4月, 2018 1 次提交
  36. 17 4月, 2018 2 次提交
  37. 03 4月, 2018 1 次提交