- 28 3月, 2014 2 次提交
-
-
由 Dr. Stephen Henson 提交于
(cherry picked from commit bc5ec653ba65fedb1619c8182088497de8a97a70)
-
由 Dr. Stephen Henson 提交于
(cherry picked from commit 1f44dac24d1cb752b1a06be9091bb03a88a8598e)
-
- 27 3月, 2014 1 次提交
-
-
由 Dr. Stephen Henson 提交于
Don't clear verification errors from the error queue unless SSL_BUILD_CHAIN_FLAG_CLEAR_ERROR is set. If errors occur during verification and SSL_BUILD_CHAIN_FLAG_IGNORE_ERROR is set return 2 so applications can issue warnings. (cherry picked from commit 2dd6976f6d02f98b30c376951ac38f780a86b3b5)
-
- 24 3月, 2014 1 次提交
-
-
由 Emilia Kasper 提交于
-
- 19 3月, 2014 1 次提交
-
-
由 Piotr Sikora 提交于
-
- 10 3月, 2014 2 次提交
-
-
由 Dr. Stephen Henson 提交于
-
由 Dr. Stephen Henson 提交于
-
- 06 3月, 2014 1 次提交
-
-
由 Andy Polyakov 提交于
Submitted by: Roumen Petrov
-
- 02 3月, 2014 1 次提交
-
-
由 Dr. Stephen Henson 提交于
Although the memory allocated by compression methods is fixed and cannot grow over time it can cause warnings in some leak checking tools. The function SSL_COMP_free_compression_methods() will free and zero the list of supported compression methods. This should *only* be called in a single threaded context when an application is shutting down to avoid interfering with existing contexts attempting to look up compression methods. (cherry picked from commit 976c58302b13d085edb3ab822f5eac4b2f1bff95)
-
- 26 2月, 2014 2 次提交
-
-
由 Dr. Stephen Henson 提交于
(cherry picked from commit 3eddd1706a30cdf3dc9278692d8ee9038eac8a0d)
-
由 Andy Polyakov 提交于
PR: 3201
-
- 25 2月, 2014 1 次提交
-
-
由 Dr. Stephen Henson 提交于
(cherry picked from commit 3678161d717d0f46c5b5b052a6d6a33438b1df00)
-
- 23 2月, 2014 2 次提交
-
-
由 Dr. Stephen Henson 提交于
When setting the current certificate check that it has a corresponding private key.
-
由 Dr. Stephen Henson 提交于
New flags to build certificate chains. The can be used to rearrange the chain so all an application needs to do is add all certificates in arbitrary order and then build the chain to check and correct them. Add verify error code when building chain. Update docs.
-
- 22 2月, 2014 1 次提交
-
-
由 Dr. Stephen Henson 提交于
-
- 21 2月, 2014 3 次提交
-
-
由 Dr. Stephen Henson 提交于
(cherry picked from commit b709f8ef54b1c9ad513878ba0213aa651a9acef8)
-
由 Dr. Stephen Henson 提交于
-
由 Dr. Stephen Henson 提交于
-
- 20 2月, 2014 2 次提交
-
-
由 Dr. Stephen Henson 提交于
-
由 Ben Laurie 提交于
-
- 19 2月, 2014 1 次提交
-
-
由 Rob Stradling 提交于
Add the extension parser in the s_client, ocsp and x509 apps.
-
- 16 2月, 2014 1 次提交
-
-
由 Dr. Stephen Henson 提交于
The flag SSL_OP_MSIE_SSLV2_RSA_PADDING hasn't done anything since OpenSSL 0.9.7h but deleting it will break source compatibility with any software that references it. Restore it but #define to zero. (cherry picked from commit b17d6b8d1d49fa4732deff17cfd1833616af0d9c)
-
- 15 2月, 2014 2 次提交
-
-
由 Rob Stradling 提交于
Add the RFC6962 OIDs to the objects table.
-
由 Andy Polyakov 提交于
-
- 13 2月, 2014 1 次提交
-
-
由 Dr. Stephen Henson 提交于
(cherry picked from commit a2317c3ffde3f1f73bd7fa3f08e420fb09043905)
-
- 06 2月, 2014 9 次提交
-
-
由 Dr. Stephen Henson 提交于
-
由 Dr. Stephen Henson 提交于
-
由 Ben Laurie 提交于
-
由 Scott Deboy 提交于
The contract for custom extension callbacks has changed - all custom extension callbacks are triggered
-
由 Ben Laurie 提交于
-
由 Scott Deboy 提交于
Whitespace fixes
-
由 Scott Deboy 提交于
-
由 Scott Deboy 提交于
If multiple TLS extensions are expected but not received, the TLS extension and supplemental data 'generate' callbacks are the only chance for the receive-side to trigger a specific TLS alert during the handshake. Removed logic which no-op'd TLS extension generate callbacks (as the generate callbacks need to always be called in order to trigger alerts), and updated the serverinfo-specific custom TLS extension callbacks to track which custom TLS extensions were received by the client, where no-ops for 'generate' callbacks are appropriate.
-
由 Dr. Stephen Henson 提交于
If an application calls the macro SSL_CTX_get_extra_chain_certs return either the old "shared" extra certificates or those associated with the current certificate. This means applications which call SSL_CTX_use_certificate_chain_file and retrieve the additional chain using SSL_CTX_get_extra_chain_certs will still work. An application which only wants to check the shared extra certificates can call the new macro SSL_CTX_get_extra_chain_certs_only
-
- 05 2月, 2014 2 次提交
-
-
由 Andy Polyakov 提交于
This allows to process multiple fragmets of maximum fragment size, as opposite to chopping maximum-sized fragments to multiple smaller ones. This approach relies on dynamic allocation of larger buffers, which we trade for performance improvement, for several *times* in some situations.
-
由 Andy Polyakov 提交于
If application has more data than maximum fragment, hold to buffer for whole write, as opposite to per-fragment strategy.
-
- 03 2月, 2014 1 次提交
-
-
由 Dr. Stephen Henson 提交于
New ctrl sets current certificate based on certain criteria. Currently two options: set the first valid certificate as current and set the next valid certificate as current. Using these an application can iterate over all certificates in an SSL_CTX or SSL structure.
-
- 28 1月, 2014 1 次提交
-
-
由 Dr. Stephen Henson 提交于
PR#3244 (cherry picked from commit 9614d2c676ffe74ce0c919d9e5c0d622a011cbed)
-
- 27 1月, 2014 1 次提交
-
-
由 Dr. Stephen Henson 提交于
-
- 26 1月, 2014 1 次提交
-
-
由 Dr. Stephen Henson 提交于
-