1. 30 3月, 2023 1 次提交
  2. 20 2月, 2023 1 次提交
  3. 11 3月, 2021 1 次提交
  4. 23 3月, 2020 1 次提交
  5. 27 2月, 2020 1 次提交
  6. 04 11月, 2019 1 次提交
  7. 28 9月, 2019 3 次提交
    • D
      Fix header file include guard names · fbbfd128
      Dr. Matthias St. Pierre 提交于
      Make the include guards consistent by renaming them systematically according
      to the naming conventions below
      
      The public header files (in the 'include/openssl' directory) are not changed
      in 1.1.1, because it is a stable release.
      
      For the private header files files, the guard names try to match the path
      specified in the include directives, with all letters converted to upper case
      and '/' and '.' replaced by '_'. An extra 'OSSL_' is added as prefix.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/9681)
      fbbfd128
    • 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
  8. 13 9月, 2019 1 次提交
  9. 10 9月, 2019 1 次提交
  10. 01 8月, 2019 1 次提交
  11. 07 6月, 2019 1 次提交
  12. 28 5月, 2019 1 次提交
  13. 24 5月, 2019 1 次提交
  14. 11 9月, 2018 1 次提交
  15. 26 8月, 2018 1 次提交
  16. 07 8月, 2018 3 次提交
  17. 26 7月, 2018 1 次提交
  18. 22 6月, 2018 1 次提交
  19. 29 5月, 2018 1 次提交
  20. 23 5月, 2018 2 次提交
    • V
      Skip CN DNS name constraint checks when not needed · 55a6250f
      Viktor Dukhovni 提交于
      Only check the CN against DNS name contraints if the
      `X509_CHECK_FLAG_NEVER_CHECK_SUBJECT` flag is not set, and either the
      certificate has no DNS subject alternative names or the
      `X509_CHECK_FLAG_ALWAYS_CHECK_SUBJECT` flag is set.
      
      Add pertinent documentation, and touch up some stale text about
      name checks and DANE.
      Reviewed-by: NMatt Caswell <matt@openssl.org>
      Reviewed-by: NTim Hudson <tjh@openssl.org>
      55a6250f
    • 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
  21. 04 5月, 2018 1 次提交
  22. 01 5月, 2018 1 次提交
  23. 27 4月, 2018 1 次提交
  24. 24 4月, 2018 1 次提交
  25. 27 2月, 2018 1 次提交
  26. 21 2月, 2018 1 次提交
  27. 20 2月, 2018 1 次提交
  28. 14 2月, 2018 1 次提交
  29. 13 2月, 2018 1 次提交
  30. 23 1月, 2018 1 次提交
  31. 08 12月, 2017 1 次提交
  32. 25 11月, 2017 1 次提交
  33. 13 11月, 2017 1 次提交
  34. 10 11月, 2017 1 次提交
  35. 27 10月, 2017 1 次提交