1. 29 5月, 2015 3 次提交
  2. 26 5月, 2015 5 次提交
  3. 23 5月, 2015 4 次提交
  4. 22 5月, 2015 1 次提交
  5. 21 5月, 2015 1 次提交
  6. 20 5月, 2015 1 次提交
  7. 19 5月, 2015 1 次提交
  8. 16 5月, 2015 3 次提交
    • M
      Version negotiation rewrite cleanup · a3680c8f
      Matt Caswell 提交于
      Following the version negotiation rewrite all of the previous code that was
      dedicated to version negotiation can now be deleted - all six source files
      of it!!
      Reviewed-by: NKurt Roeckx <kurt@openssl.org>
      a3680c8f
    • M
      Client side version negotiation rewrite · 13c9bb3e
      Matt Caswell 提交于
      Continuing from the previous commit this changes the way we do client side
      version negotiation. Similarly all of the s23* "up front" state machine code
      has been avoided and again things now work much the same way as they already
      did for DTLS, i.e. we just do most of the work in the
      ssl3_get_server_hello() function.
      Reviewed-by: NKurt Roeckx <kurt@openssl.org>
      13c9bb3e
    • M
      Server side version negotiation rewrite · 32ec4153
      Matt Caswell 提交于
      This commit changes the way that we do server side protocol version
      negotiation. Previously we had a whole set of code that had an "up front"
      state machine dedicated to the negotiating the protocol version. This adds
      significant complexity to the state machine. Historically the justification
      for doing this was the support of SSLv2 which works quite differently to
      SSLv3+. However, we have now removed support for SSLv2 so there is little
      reason to maintain this complexity.
      
      The one slight difficulty is that, although we no longer support SSLv2, we
      do still support an SSLv3+ ClientHello in an SSLv2 backward compatible
      ClientHello format. This is generally only used by legacy clients. This
      commit adds support within the SSLv3 code for these legacy format
      ClientHellos.
      
      Server side version negotiation now works in much the same was as DTLS,
      i.e. we introduce the concept of TLS_ANY_VERSION. If s->version is set to
      that then when a ClientHello is received it will work out the most
      appropriate version to respond with. Also, SSLv23_method and
      SSLv23_server_method have been replaced with TLS_method and
      TLS_server_method respectively. The old SSLv23* names still exist as
      macros pointing at the new name, although they are deprecated.
      
      Subsequent commits will look at client side version negotiation, as well of
      removal of the old s23* code.
      Reviewed-by: NKurt Roeckx <kurt@openssl.org>
      32ec4153
  9. 15 5月, 2015 1 次提交
  10. 14 5月, 2015 2 次提交
  11. 13 5月, 2015 2 次提交
  12. 11 5月, 2015 3 次提交
  13. 07 5月, 2015 2 次提交
    • R
      Use "==0" instead of "!strcmp" etc · 86885c28
      Rich Salz 提交于
      For the various string-compare routines (strcmp, strcasecmp, str.*cmp)
      use "strcmp()==0" instead of "!strcmp()"
      Reviewed-by: NTim Hudson <tjh@openssl.org>
      86885c28
    • R
      Make -CAserial a type 's' option · 5c4e3a4e
      Richard Levitte 提交于
      The file name given to -CAserial might not exist yet.  The
      -CAcreateserial option decides if this is ok or not.
      
      Previous to this change, -CAserial was a type '<' option, and in that
      case, the existence of the file given as argument is tested quite
      early, and is a failure if it doesn't.  With the type 's' option, the
      argument is just a string that the application can do whatever it
      wants with.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      5c4e3a4e
  14. 06 5月, 2015 4 次提交
    • G
      Initialize potentially uninitialized local variables · 4c9b0a03
      Gunnar Kudrjavets 提交于
      Compiling OpenSSL code with MSVC and /W4 results in a number of warnings.
      One category of warnings is particularly interesting - C4701 (potentially
      uninitialized local variable 'name' used). This warning pretty much means
      that there's a code path which results in uninitialized variables being used
      or returned. Depending on compiler, its options, OS, values in registers
      and/or stack, the results can be nondeterministic. Cases like this are very
      hard to debug so it's rational to fix these issues.
      
      This patch contains a set of trivial fixes for all the C4701 warnings (just
      initializing variables to 0 or NULL or appropriate error code) to make sure
      that deterministic values will be returned from all the execution paths.
      
      RT#3835
      Signed-off-by: NMatt Caswell <matt@openssl.org>
      
      Matt's note: All of these appear to be bogus warnings, i.e. there isn't
      actually a code path where an unitialised variable could be used - its just
      that the compiler hasn't been able to figure that out from the logic. So
      this commit is just about silencing spurious warnings.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      4c9b0a03
    • M
      Fix s_server version specific methods · 4407d070
      Matt Caswell 提交于
      A copy&paste error as a result of the big apps cleanup broke the version
      specific methods in s_server.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      4407d070
    • R
      memset, memcpy, sizeof consistency fixes · 16f8d4eb
      Rich Salz 提交于
      Just as with the OPENSSL_malloc calls, consistently use sizeof(*ptr)
      for memset and memcpy.  Remove needless casts for those functions.
      For memset, replace alternative forms of zero with 0.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      16f8d4eb
    • M
      Fix windows build · b1ad95e3
      Matt Caswell 提交于
      Fix error in WIN32_rename() introduced by commit b4faea50.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      b1ad95e3
  15. 05 5月, 2015 5 次提交
  16. 04 5月, 2015 2 次提交