1. 31 7月, 2001 1 次提交
  2. 30 7月, 2001 1 次提交
  3. 22 2月, 2001 1 次提交
  4. 20 2月, 2001 1 次提交
  5. 16 12月, 2000 1 次提交
  6. 30 11月, 2000 1 次提交
  7. 17 11月, 2000 1 次提交
  8. 18 9月, 2000 1 次提交
  9. 02 6月, 2000 1 次提交
    • R
      There have been a number of complaints from a number of sources that names · 26a3a48d
      Richard Levitte 提交于
      like Malloc, Realloc and especially Free conflict with already existing names
      on some operating systems or other packages.  That is reason enough to change
      the names of the OpenSSL memory allocation macros to something that has a
      better chance of being unique, like prepending them with OPENSSL_.
      
      This change includes all the name changes needed throughout all C files.
      26a3a48d
  10. 01 6月, 2000 1 次提交
    • G
      The previous commit to crypto/stack/*.[ch] pulled the type-safety strings · ccd86b68
      Geoff Thorpe 提交于
      yet tighter, and also put some heat on the rest of the library by
      insisting (correctly) that compare callbacks used in stacks are prototyped
      with "const" parameters. This has led to a depth-first explosion of
      compiler warnings in the code where 1 constification has led to 3 or 4
      more. Fortunately these have all been resolved to completion and the code
      seems cleaner as a result - in particular many of the _cmp() functions
      should have been prototyped with "const"s, and now are. There was one
      little problem however;
      
      X509_cmp() should by rights compare "const X509 *" pointers, and it is now
      declared as such. However, it's internal workings can involve
      recalculating hash values and extensions if they have not already been
      setup. Someone with a more intricate understanding of the flow control of
      X509 might be able to tighten this up, but for now - this seemed the
      obvious place to stop the "depth-first" constification of the code by
      using an evil cast (they have migrated all the way here from safestack.h).
      
      Fortunately, this is the only place in the code where this was required
      to complete these type-safety changes, and it's reasonably clear and
      commented, and seemed the least unacceptable of the options. Trying to
      take the constification further ends up exploding out considerably, and
      indeed leads directly into generalised ASN functions which are not likely
      to cooperate well with this.
      ccd86b68
  11. 21 5月, 2000 1 次提交
  12. 14 3月, 2000 2 次提交
    • B
      Use correct function names in SSLerr macros. · 448e2f9b
      Bodo Möller 提交于
      448e2f9b
    • B
      Copy DH key (if available) in addition to the bare parameters · e11f0de6
      Bodo Möller 提交于
      in SSL_new.
      If SSL_OP_SINGLE_DH_USE is set, don't waste time in SSL_[CTX_]set_tmp_dh
      on computing a DH key that will be ignored anyway.
      
      ssltest -dhe1024dsa (w/ 160-bit sub-prime) had an unfair performance
      advantage over -dhe1024 (safe prime): SSL_OP_SINGLE_DH_USE was
      effectively always enabled because SSL_new ignored the DH key set in
      the SSL_CTX.  Now -dhe1024 takes the server only about twice as long
      as -dhe1024dsa instead of three times as long (for 1024 bit RSA
      with 1024 bit DH).
      e11f0de6
  13. 24 1月, 2000 1 次提交
    • D
      · dd9d233e
      Dr. Stephen Henson 提交于
      Tidy up CRYPTO_EX_DATA structures.
      dd9d233e
  14. 30 11月, 1999 1 次提交
  15. 12 9月, 1999 1 次提交
    • A
      Initial support for MacOS. · 17f389bb
      Andy Polyakov 提交于
      This will soon be complemented with MacOS specific source code files and
      INSTALL.MacOS.
      
      I (Andy) have decided to get rid of a number of #include <sys/types.h>.
      I've verified it's ok (both by examining /usr/include/*.h and compiling)
      on a number of Unix platforms. Unfortunately I don't have Windows box
      to verify this on. I really appreciate if somebody could try to compile
      it and contact me a.s.a.p. in case a problem occurs.
      
      Submitted by: Roy Wood <roy@centricsystems.ca>
      Reviewed by: Andy Polyakov <appro@fy.chalmers.se>
      17f389bb
  16. 08 8月, 1999 1 次提交
  17. 30 7月, 1999 1 次提交
  18. 22 7月, 1999 1 次提交
  19. 30 5月, 1999 1 次提交
  20. 21 5月, 1999 1 次提交
  21. 14 5月, 1999 1 次提交
  22. 13 5月, 1999 3 次提交
  23. 10 5月, 1999 2 次提交
  24. 09 5月, 1999 1 次提交
  25. 04 5月, 1999 1 次提交
  26. 01 5月, 1999 1 次提交
  27. 24 4月, 1999 1 次提交
  28. 20 4月, 1999 1 次提交
  29. 13 4月, 1999 1 次提交
  30. 22 3月, 1999 1 次提交
  31. 06 3月, 1999 1 次提交
  32. 03 3月, 1999 1 次提交
  33. 01 3月, 1999 1 次提交
  34. 27 2月, 1999 1 次提交
  35. 25 2月, 1999 1 次提交
    • R
      Add a bunch of SSL_xxx() functions for configuring the temporary RSA and DH · 15d21c2d
      Ralf S. Engelschall 提交于
      private keys and/or callback functions which directly correspond to their
      SSL_CTX_xxx() counterparts but work on a per-connection basis. This is needed
      for applications which have to configure certificates on a per-connection
      basis (e.g. Apache+mod_ssl) instead of a per-context basis (e.g.
      s_server).
      
      For the RSA certificate situation is makes no difference, but for the DSA
      certificate situation this fixes the "no shared cipher" problem where the
      OpenSSL cipher selection procedure failed because the temporary keys were not
      overtaken from the context and the API provided no way to reconfigure them.
      
      The new functions now let applications reconfigure the stuff and they are in
      detail: SSL_need_tmp_RSA, SSL_set_tmp_rsa, SSL_set_tmp_dh,
      SSL_set_tmp_rsa_callback and SSL_set_tmp_dh_callback.  Additionally a new
      non-public-API function ssl_cert_instantiate() is used as a helper function
      and also to reduce code redundancy inside ssl_rsa.c.
      
      Submitted by: Ralf S. Engelschall
      Reviewed by: Ben Laurie
      15d21c2d
  36. 08 1月, 1999 1 次提交