1. 26 Oct, 2017 1 commit
  2. 25 Oct, 2017 1 commit
  3. 24 Oct, 2017 4 commits
  4. 23 Oct, 2017 2 commits
  5. 22 Oct, 2017 1 commit
  6. 20 Oct, 2017 1 commit
  7. 19 Oct, 2017 1 commit
  8. 17 Oct, 2017 3 commits
  9. 13 Oct, 2017 2 commits
  10. 11 Oct, 2017 6 commits
  11. 09 Oct, 2017 6 commits
  12. 08 Oct, 2017 1 commit
  13. 06 Oct, 2017 1 commit
  14. 05 Oct, 2017 2 commits
  15. 04 Oct, 2017 2 commits
  16. 02 Oct, 2017 1 commit
  17. 30 Sep, 2017 2 commits
  18. 29 Sep, 2017 2 commits
  19. 27 Sep, 2017 1 commit
    • David Benjamin's avatar
      Allow DH_set0_key with only private key. · effdcf6c
      David Benjamin authored
      The pub_key field for DH isn't actually used in DH_compute_key at all.
      (Note the peer public key is passed in as as BIGNUM.) It's mostly there
      so the caller may extract it from DH_generate_key. It doesn't
      particularly need to be present if filling in a DH from external
      parameters.
      
      The check in DH_set0_key conflicts with adding OpenSSL 1.1.0 to Node.
      Their public API is a thin wrapper over the old OpenSSL one:
      https://nodejs.org/api/crypto.html#crypto_class_diffiehellman
      
      
      
      They have separate setPrivateKey and setPublicKey methods, so the public
      key may be set last or not at all. In 1.0.2, either worked fine since
      operations on DH objects generally didn't use the public key.  (Like
      with OpenSSL, Node's setPublicKey method is also largely a no-op, but so
      it goes.) In 1.1.0, DH_set0_key prevents create a private-key-only DH
      object.
      
      (cherry picked from commit d58ad9a2a287d1c0bc99ba63c997eed88cc161b5)
      
      Reviewed-by: default avatarRich Salz <rsalz@openssl.org>
      Reviewed-by: default avatarBernd Edlinger <bernd.edlinger@hotmail.de>
      (Merged from https://github.com/openssl/openssl/pull/4425)
      effdcf6c