1. 19 6月, 2018 1 次提交
  2. 25 4月, 2018 1 次提交
    • N
      [SM2_sign] add minimal EVP_PKEY functionality testing · 22f0c72b
      Nicola Tuveri 提交于
      The actual functionality of generating signatures through the `EVP_PKEY`
      API is completely untested.
      Current tests under the `EVP_PKEY` API
      (`test/recipes/30-test_evp_data/evppkey.txt`) only cover `Verify` and
      `Decrypt`, while encryption and signature generation are tested with
      ad-hoc clients (`test/sm2crypttest.c`, `test/sm2signtest.c`) that do not
      call the `EVP_PKEY` interface at all but soon-to-be private functions
      that bypass it (cf. PR#5895 ).
      
      It is my opinion that an ideal solution for the future would consist on
      enhancing the `test/evp_pkey` facility and syntax to allow tests to take
      control of the PRNG to inject known nonces and validate the results of
      `EVP_PKEY` implementations against deterministic known answer tests, but
      it is probably too late to work on this feature in time for next release.
      
      Given that commit b5a85f70d8 highlights some critical bugs in the hook
      between the `EVP_PKEY` interface and SM2 signature generation and that
      these defects escaped testing and code review, I think that at least for
      now it is beneficial to at least add the kind of "bogus" testing
      provided by this patch:
      this is a "fake" test as it does only verify that the SM2 `EVP_PKEY`
      interface is capable of creating a signature without failing, but it
      does not say anything about the generated signature being valid, nor
      does it test the functional correctness of the cryptosystem.
      Reviewed-by: NBernd Edlinger <bernd.edlinger@hotmail.de>
      Reviewed-by: NMatt Caswell <matt@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/6066)
      22f0c72b
  3. 20 3月, 2018 1 次提交
  4. 19 3月, 2018 3 次提交
  5. 15 3月, 2018 1 次提交
  6. 02 3月, 2018 1 次提交
  7. 12 10月, 2017 1 次提交
  8. 19 7月, 2017 1 次提交
  9. 16 6月, 2017 1 次提交
  10. 06 6月, 2017 1 次提交
  11. 31 5月, 2017 1 次提交
  12. 23 5月, 2017 1 次提交
  13. 20 5月, 2017 1 次提交
  14. 13 5月, 2017 1 次提交
  15. 12 5月, 2017 2 次提交
  16. 28 4月, 2017 1 次提交
  17. 26 4月, 2017 1 次提交
  18. 14 4月, 2017 2 次提交
  19. 12 4月, 2017 2 次提交
  20. 17 3月, 2017 1 次提交
  21. 15 3月, 2017 1 次提交
  22. 01 3月, 2017 1 次提交
  23. 28 2月, 2017 2 次提交
  24. 21 2月, 2017 1 次提交
  25. 02 2月, 2017 1 次提交
  26. 24 1月, 2017 1 次提交
  27. 18 1月, 2017 2 次提交
  28. 08 1月, 2017 2 次提交
  29. 02 1月, 2017 2 次提交
  30. 15 12月, 2016 1 次提交
  31. 12 12月, 2016 1 次提交