Skip to content

T
Third Party Openssl

OpenHarmony / Third Party Openssl
1 年多 前同步成功

通知 10
Star 18
Fork 1
T
Third Party Openssl
切换分支/标签
  1. 30 3月, 2023 1 次提交
  3. 27 2月, 2020 1 次提交
  5. 29 10月, 2019 1 次提交
  7. 28 9月, 2019 1 次提交
    • 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
  9. 10 9月, 2019 1 次提交
  11. 01 8月, 2019 1 次提交
  13. 17 10月, 2018 1 次提交
  15. 12 9月, 2018 1 次提交
  17. 11 9月, 2018 1 次提交
  19. 07 9月, 2018 5 次提交
  21. 29 8月, 2018 1 次提交
  23. 31 7月, 2018 1 次提交
  25. 26 7月, 2018 1 次提交
  27. 24 7月, 2018 1 次提交
  29. 07 7月, 2018 4 次提交
  31. 25 6月, 2018 1 次提交
  33. 19 6月, 2018 1 次提交
  35. 05 6月, 2018 1 次提交
  37. 04 6月, 2018 7 次提交
  39. 25 4月, 2018 1 次提交
    • N
      [SM2_sign] fix double free and return value · 67cc2bae
      由 Nicola Tuveri 提交于 
      Currently, critical bugs prevent using SM2 signatures through the
`EVP_PKEY` interface: any application that managed to satisfy the
requirement of forcing SM3 as the message digest – even if this is
currently not possible transparently through the `EVP_PKEY` interface
and requires manually forcing the MD selection – would crash with a
segmentation fault upon calling the `SM2_sign()` function.

This is easily verified using the OpenSSL CLI to execute this critical
code path under the right conditions:
`openssl dgst -sm3 -hex -sign sm2.eckey /path/to/file/to/sign`

The issue is caused by a double free at the end of `SM2_sign()` in
`crypto/sm2/sm2_sign.c` in case of successful signature generation.
In addition, even if the double free was not causing segfaults,
the function returns the wrong return value in case of success (it
would return 0 rather than 1).

This patch fixes both problems.
Reviewed-by: NBernd Edlinger <bernd.edlinger@hotmail.de>
Reviewed-by: NMatt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/6066)
      67cc2bae
  41. 20 3月, 2018 1 次提交
  43. 19 3月, 2018 3 次提交