1. 18 10月, 2007 1 次提交
  2. 12 8月, 2007 1 次提交
  3. 07 6月, 2007 1 次提交
  4. 21 3月, 2007 1 次提交
  5. 10 2月, 2007 1 次提交
  6. 30 11月, 2006 2 次提交
  7. 30 3月, 2006 1 次提交
  8. 13 3月, 2006 1 次提交
  9. 12 3月, 2006 1 次提交
  10. 11 3月, 2006 1 次提交
  11. 10 1月, 2006 1 次提交
  12. 06 1月, 2006 1 次提交
  13. 03 1月, 2006 2 次提交
  14. 31 12月, 2005 1 次提交
  15. 06 12月, 2005 1 次提交
  16. 15 8月, 2005 1 次提交
  17. 30 4月, 2005 1 次提交
  18. 27 4月, 2005 1 次提交
  19. 30 3月, 2005 1 次提交
  20. 28 12月, 2003 1 次提交
  21. 08 9月, 2003 1 次提交
  22. 16 2月, 2003 1 次提交
  23. 28 11月, 2002 1 次提交
  24. 13 11月, 2002 1 次提交
  25. 29 10月, 2002 1 次提交
    • G
      Correct and enhance the behaviour of "internal" session caching as it · e0db2eed
      Geoff Thorpe 提交于
      relates to SSL_CTX flags and the use of "external" session caching. The
      existing flag, "SSL_SESS_CACHE_NO_INTERNAL_LOOKUP" remains but is
      supplemented with a complimentary flag, "SSL_SESS_CACHE_NO_INTERNAL_STORE".
      The bitwise OR of the two flags is also defined as
      "SSL_SESS_CACHE_NO_INTERNAL" and is the flag that should be used by most
      applications wanting to implement session caching *entirely* by its own
      provided callbacks. As the documented behaviour contradicted actual
      behaviour up until recently, and since that point behaviour has itself been
      inconsistent anyway, this change should not introduce any compatibility
      problems. I've adjusted the relevant documentation to elaborate about how
      this works.
      
      Kudos to "Nadav Har'El" <nyh@math.technion.ac.il> for diagnosing these
      anomalies and testing this patch for correctness.
      
      PR: 311
      e0db2eed
  26. 02 8月, 2002 1 次提交
  27. 30 7月, 2002 1 次提交
    • L
      OpenSSL Security Advisory [30 July 2002] · c046fffa
      Lutz Jänicke 提交于
      Changes marked "(CHATS)" were sponsored by the Defense Advanced
      Research Projects Agency (DARPA) and Air Force Research Laboratory,
      Air Force Materiel Command, USAF, under agreement number
      F30602-01-2-0537.
      c046fffa
  28. 10 2月, 2002 1 次提交
  29. 02 9月, 2001 1 次提交
    • G
      Make the necessary changes to work with the recent "ex_data" overhaul. · 79aa04ef
      Geoff Thorpe 提交于
      See the commit log message for that for more information.
      
      NB: X509_STORE_CTX's use of "ex_data" support was actually misimplemented
      (initialisation by "memset" won't/can't/doesn't work). This fixes that but
      requires that X509_STORE_CTX_init() be able to handle errors - so its
      prototype has been changed to return 'int' rather than 'void'. All uses of
      that function throughout the source code have been tracked down and
      adjusted.
      79aa04ef
  30. 13 8月, 2001 1 次提交
    • G
      The indexes returned by ***_get_ex_new_index() functions are used when · b7727ee6
      Geoff Thorpe 提交于
      setting stack (actually, array) values in ex_data. So only increment the
      global counters if the underlying CRYPTO_get_ex_new_index() call succeeds.
      This change doesn't make "ex_data" right (see the comment at the head of
      ex_data.c to know why), but at least makes the source code marginally less
      frustrating.
      b7727ee6
  31. 31 7月, 2001 2 次提交
  32. 23 2月, 2001 1 次提交
    • G
      Fix an oversight - when checking a potential session ID for conflicts with · f85c9904
      Geoff Thorpe 提交于
      an SSL_CTX's session cache, it is necessary to compare the ssl_version at
      the same time (a conflict is defined, courtesy of SSL_SESSION_cmp(), as a
      matching id/id_length pair and a matching ssl_version). However, the
      SSL_SESSION that will result from the current negotiation does not
      necessarily have the same ssl version as the "SSL_METHOD" in use by the
      SSL_CTX - part of the work in a handshake is to agree on an ssl version!
      
      This is fixed by having the check function accept an SSL pointer rather
      than the SSL_CTX it belongs to.
      
      [Thanks to Lutz for illuminating the full extent of my stupidity]
      f85c9904
  33. 22 2月, 2001 1 次提交
    • G
      This change allows a callback to be used to override the generation of · dc644fe2
      Geoff Thorpe 提交于
      SSL/TLS session IDs in a server. According to RFC2246, the session ID is an
      arbitrary value chosen by the server. It can be useful to have some control
      over this "arbitrary value" so as to choose it in ways that can aid in
      things like external session caching and balancing (eg. clustering). The
      default session ID generation is to fill the ID with random data.
      
      The callback used by default is built in to ssl_sess.c, but registering a
      callback in an SSL_CTX or in a particular SSL overrides this. BTW: SSL
      callbacks will override SSL_CTX callbacks, and a new SSL structure inherits
      any callback set in its 'parent' SSL_CTX. The header comments describe how
      this mechanism ticks, and source code comments describe (hopefully) why it
      ticks the way it does.
      
      Man pages are on the way ...
      
      [NB: Lutz was also hacking away and helping me to figure out how best to do
      this.]
      dc644fe2
  34. 09 1月, 2001 1 次提交
  35. 02 12月, 2000 1 次提交
    • G
      First step in tidying up the LHASH code. The callback prototypes (and · 385d8138
      Geoff Thorpe 提交于
      casts) used in the lhash code are about as horrible and evil as they can
      be. For starters, the callback prototypes contain empty parameter lists.
      Yuck.
      
      This first change defines clearer prototypes - including "typedef"'d
      function pointer types to use as "hash" and "compare" callbacks, as well as
      the callbacks passed to the lh_doall and lh_doall_arg iteration functions.
      Now at least more explicit (and clear) casting is required in all of the
      dependant code - and that should be included in this commit.
      
      The next step will be to hunt down and obliterate some of the function
      pointer casting being used when it's not necessary - a particularly evil
      variant exists in the implementation of lh_doall.
      385d8138
  36. 30 11月, 2000 1 次提交
  37. 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