1. 24 5月, 2016 9 次提交
  2. 23 5月, 2016 17 次提交
  3. 22 5月, 2016 4 次提交
  4. 21 5月, 2016 4 次提交
  5. 20 5月, 2016 6 次提交
    • R
      Rename lh_xxx,sk_xxx tp OPENSSL_{LH,SK}_xxx · 739a1eb1
      Rich Salz 提交于
      Rename sk_xxx to OPENSSL_sk_xxx and _STACK to OPENSSL_STACK
      Rename lh_xxx API to OPENSSL_LH_xxx and LHASH_NODE to OPENSSL_LH_NODE
      Make lhash stuff opaque.
      Use typedefs for function pointers; makes the code simpler.
      Remove CHECKED_xxx macros.
      Add documentation; remove old X509-oriented doc.
      Add API-compat names for entire old API
      Reviewed-by: NDr. Stephen Henson <steve@openssl.org>
      739a1eb1
    • R
      06593767
    • R
      VMS: setbuf() only takes 32-bit pointers · 8ff889c2
      Richard Levitte 提交于
      Giving setbuf() a 64-bit pointer isn't faulty, as the argument is
      passed by a 64-bit register anyway, so you only get a warning
      (MAYLOSEDATA2) pointing out that only the least significant 32 bits
      will be used.
      
      However, we know that a FILE* returned by fopen() and such really is a
      32-bit pointer (a study of the system header files make that clear),
      so we temporarly turn off that warning when calling setbuf().
      Reviewed-by: NAndy Polyakov <appro@openssl.org>
      8ff889c2
    • M
      Add an async io test · d7295cd6
      Matt Caswell 提交于
      This adds an async IO test. There are two test runs. The first one does
      a normal handshake with lots of async IO events. The second one does the
      same but this time breaks up all the written records into multiple records
      of one byte in length. We do this all the way up until the CCS.
      Reviewed-by: NAndy Polyakov <appro@openssl.org>
      d7295cd6
    • M
      Ensure async IO works with new state machine · 1689e7e6
      Matt Caswell 提交于
      In the new state machine if using nbio and we get the header of a
      handshake message is one record with the body in the next, with an nbio
      event in the middle, then the connection was failing. This is because
      s->init_num was getting reset. We should only reset it after we have
      read the whole message.
      
      RT#4394
      Reviewed-by: NAndy Polyakov <appro@openssl.org>
      1689e7e6
    • D
      Tighten up logic around ChangeCipherSpec. · 1257adec
      David Benjamin 提交于
      ChangeCipherSpec messages have a defined value. They also may not occur
      in the middle of a handshake message. The current logic will accept a
      ChangeCipherSpec with value 2. It also would accept up to three bytes of
      handshake data before the ChangeCipherSpec which it would discard
      (because s->init_num gets reset).
      
      Instead, require that s->init_num is 0 when a ChangeCipherSpec comes in.
      
      RT#4391
      Reviewed-by: NAndy Polyakov <appro@openssl.org>
      Reviewed-by: NMatt Caswell <matt@openssl.org>
      1257adec