1. 14 3月, 2020 1 次提交
    • B
      Additional updates to SSL_CTX_sess_set_get_cb.pod · d3133cc7
      Benjamin Kaduk 提交于
      Generally modernize the language.
      
      Refer to TLS instead of SSL/TLS, and try to have more consistent
      usage of commas and that/which.
      
      Reword some descriptions to avoid implying that a list of potential
      reasons for behavior is an exhaustive list.
      
      Clarify how get_session_cb() is only called on servers (i.e., in general,
      and that it's given the session ID proposed by the client).
      
      Clarify the semantics of the get_cb()'s "copy" argument.
      The behavior seems to have changed in commit
      8876bc05, though the behavior prior
      to that commit was not to leave the reference-count unchanged if
      *copy was not written to -- instead, libssl seemed to assume that the
      callback already had incremented the reference count.
      Reviewed-by: NTomas Mraz <tmraz@fedoraproject.org>
      (Merged from https://github.com/openssl/openssl/pull/10943)
      
      (cherry picked from commit 06f876837a8ec76b28c42953731a156c0c3700e2)
      d3133cc7
  2. 13 3月, 2020 1 次提交
  3. 12 3月, 2020 1 次提交
  4. 09 3月, 2020 3 次提交
  5. 08 3月, 2020 1 次提交
  6. 07 3月, 2020 1 次提交
  7. 06 3月, 2020 2 次提交
  8. 27 2月, 2020 1 次提交
  9. 15 2月, 2020 1 次提交
  10. 06 2月, 2020 3 次提交
  11. 31 1月, 2020 1 次提交
  12. 30 1月, 2020 1 次提交
  13. 25 1月, 2020 1 次提交
  14. 17 1月, 2020 1 次提交
  15. 15 1月, 2020 1 次提交
  16. 09 1月, 2020 1 次提交
  17. 19 12月, 2019 1 次提交
  18. 16 12月, 2019 2 次提交
  19. 12 12月, 2019 2 次提交
  20. 09 12月, 2019 1 次提交
  21. 28 11月, 2019 1 次提交
  22. 27 11月, 2019 1 次提交
  23. 17 11月, 2019 1 次提交
  24. 14 11月, 2019 1 次提交
    • N
      Extend docs for EC_POINT conversion functions · 3c25ac2d
      Nicola Tuveri 提交于
      Add more explicit documentation about the relation between
      EC_POINT_point2oct(), EC_POINT_point2hex(), EC_POINT_point2bn() and
      their reverse.
      
      In particular highlight that EC_POINT_point2oct() and
      EC_POINT_oct2point() conform to, respectively, Sec. 2.3.3 and Sec. 2.3.4
      of the SECG SEC 1 standard (which is the normative reference for the
      already mentioned RFC 5480), highlighting with a note how this affect
      the encoding/decoding of the point at infinity (which in contrast with
      any other valid generic point of a curve is assigned an exceptional
      fixed octet string encoding, i.e., 0x00).
      Reviewed-by: NMatt Caswell <matt@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/10329)
      
      (cherry picked from commit 3cc26f2eba8a8c16ac559e68c05c094d7ea6bd8b)
      3c25ac2d
  25. 12 11月, 2019 1 次提交
  26. 31 10月, 2019 1 次提交
  27. 28 10月, 2019 1 次提交
  28. 23 10月, 2019 3 次提交
  29. 22 10月, 2019 1 次提交
  30. 15 10月, 2019 2 次提交