1. 15 4月, 2009 1 次提交
  2. 19 3月, 2009 1 次提交
  3. 03 3月, 2009 1 次提交
  4. 15 2月, 2009 2 次提交
  5. 30 12月, 2008 1 次提交
  6. 29 12月, 2008 1 次提交
  7. 02 12月, 2008 1 次提交
  8. 12 11月, 2008 1 次提交
  9. 11 11月, 2008 1 次提交
  10. 06 11月, 2008 1 次提交
  11. 04 11月, 2008 1 次提交
  12. 02 11月, 2008 3 次提交
  13. 01 11月, 2008 1 次提交
  14. 22 10月, 2008 1 次提交
  15. 20 10月, 2008 1 次提交
  16. 12 10月, 2008 1 次提交
  17. 15 8月, 2008 1 次提交
  18. 06 8月, 2008 1 次提交
    • G
      Remove the dual-callback scheme for numeric and pointer thread IDs, · 4c329696
      Geoff Thorpe 提交于
      deprecate the original (numeric-only) scheme, and replace with the
      CRYPTO_THREADID object. This hides the platform-specifics and should reduce
      the possibility for programming errors (where failing to explicitly check
      both thread ID forms could create subtle, platform-specific bugs).
      
      Thanks to Bodo, for invaluable review and feedback.
      4c329696
  19. 05 7月, 2008 1 次提交
  20. 04 7月, 2008 1 次提交
  21. 04 6月, 2008 1 次提交
  22. 28 3月, 2008 1 次提交
    • G
      There was a need to support thread ID types that couldn't be reliably cast · f7ccba3e
      Geoff Thorpe 提交于
      to 'unsigned long' (ie. odd platforms/compilers), so a pointer-typed
      version was added but it required portable code to check *both* modes to
      determine equality. This commit maintains the availability of both thread
      ID types, but deprecates the type-specific accessor APIs that invoke the
      callbacks - instead a single type-independent API is used.  This simplifies
      software that calls into this interface, and should also make it less
      error-prone - as forgetting to call and compare *both* thread ID accessors
      could have led to hard-to-debug/infrequent bugs (that might only affect
      certain platforms or thread implementations). As the CHANGES note says,
      there were corresponding deprecations and replacements in the
      thread-related functions for BN_BLINDING and ERR too.
      f7ccba3e
  23. 23 3月, 2008 1 次提交
  24. 17 3月, 2008 1 次提交
  25. 13 3月, 2008 1 次提交
    • D
      And so it begins... · 8931b30d
      Dr. Stephen Henson 提交于
      Initial support for CMS.
      
      Add zlib compression BIO.
      
      Add AES key wrap implementation.
      
      Generalize S/MIME MIME code to support CMS and/or PKCS7.
      8931b30d
  26. 26 10月, 2007 1 次提交
    • D
      1. Changes for s_client.c to make it return non-zero exit code in case · 0e1dba93
      Dr. Stephen Henson 提交于
      of handshake failure
      
      2. Changes to x509_certificate_type function (crypto/x509/x509type.c) to
      make it recognize GOST certificates as EVP_PKT_SIGN|EVP_PKT_EXCH
      (required for s3_srvr to accept GOST client certificates).
      
      3. Changes to EVP
      	- adding of function EVP_PKEY_CTX_get0_peerkey
      	- Make function EVP_PKEY_derive_set_peerkey work for context with
      	  ENCRYPT operation, because we use peerkey field in the context to
      	  pass non-ephemeral secret key to GOST encrypt operation.
      	- added EVP_PKEY_CTRL_SET_IV control command. It is really
      	  GOST-specific, but it is used in SSL code, so it has to go
      	  in some header file, available during libssl compilation
      
      4. Fix to HMAC to avoid call of OPENSSL_cleanse on undefined data
      
      5. Include des.h if KSSL_DEBUG is defined into some libssl files, to
        make debugging output which depends on constants defined there, work
        and other KSSL_DEBUG output fixes
      
      6. Declaration of real GOST ciphersuites, two authentication methods
         SSL_aGOST94 and SSL_aGOST2001 and one key exchange method SSL_kGOST
      
      7. Implementation  of these methods.
      
      8. Support for sending unsolicited serverhello extension if GOST
        ciphersuite is selected. It is require for interoperability with
        CryptoPro CSP 3.0 and 3.6 and controlled by
        SSL_OP_CRYPTOPRO_TLSEXT_BUG constant.
        This constant is added to SSL_OP_ALL, because it does nothing, if
        non-GOST ciphersuite is selected, and all implementation of GOST
        include compatibility with CryptoPro.
      
      9. Support for CertificateVerify message without length field. It is
         another CryptoPro bug, but support is made unconditional, because it
         does no harm for draft-conforming implementation.
      
      10. In tls1_mac extra copy of stream mac context is no more done.
        When I've written currently commited code I haven't read
        EVP_DigestSignFinal manual carefully enough and haven't noticed that
        it does an internal digest ctx copying.
      
      This implementation was tested against
      1. CryptoPro CSP 3.6 client and server
      2. Cryptopro CSP 3.0 server
      0e1dba93
  27. 13 10月, 2007 1 次提交
  28. 09 7月, 2007 1 次提交
  29. 31 5月, 2007 1 次提交
  30. 18 5月, 2007 1 次提交
  31. 16 5月, 2007 1 次提交
  32. 24 4月, 2007 1 次提交
  33. 12 4月, 2007 2 次提交
  34. 11 4月, 2007 1 次提交
  35. 09 4月, 2007 1 次提交
  36. 08 4月, 2007 1 次提交