- 08 7月, 2012 1 次提交
-
-
由 Dr. Stephen Henson 提交于
details in s_client. Also add ctrl to set client certificate types. If not used sensible values will be included based on supported signature algorithms: for example if we don't include any DSA signing algorithms the DSA certificate type is omitted. Fix restriction in old code where certificate types would be truncated if it exceeded TLS_CT_NUMBER.
-
- 05 7月, 2012 2 次提交
-
-
由 Richard Levitte 提交于
-
由 Richard Levitte 提交于
-
- 03 7月, 2012 3 次提交
-
-
由 Dr. Stephen Henson 提交于
-
由 Dr. Stephen Henson 提交于
-
由 Dr. Stephen Henson 提交于
the permitted signature algorithms for server and client authentication are the same but it is now possible to set different algorithms for client authentication only.
-
- 29 6月, 2012 1 次提交
-
-
由 Dr. Stephen Henson 提交于
is required by client or server. An application can decide which certificate chain to present based on arbitrary criteria: for example supported signature algorithms. Add very simple example to s_server. This fixes many of the problems and restrictions of the existing client certificate callback: for example you can now clear existing certificates and specify the whole chain.
-
- 28 6月, 2012 2 次提交
-
-
由 Dr. Stephen Henson 提交于
appropriate checks in tls1_check_chain.
-
由 Dr. Stephen Henson 提交于
the certificate can be used for (if anything). Set valid_flags field in new tls1_check_chain function. Simplify ssl_set_cert_masks which used to have similar checks in it. Add new "cert_flags" field to CERT structure and include a "strict mode". This enforces some TLS certificate requirements (such as only permitting certificate signature algorithms contained in the supported algorithms extension) which some implementations ignore: this option should be used with caution as it could cause interoperability issues.
-
- 27 6月, 2012 1 次提交
-
-
由 Dr. Stephen Henson 提交于
-
- 25 6月, 2012 1 次提交
-
-
由 Dr. Stephen Henson 提交于
Only store encoded versions of peer and configured signature algorithms. Determine shared signature algorithms and cache the result along with NID equivalents of each algorithm.
-
- 22 6月, 2012 1 次提交
-
-
由 Dr. Stephen Henson 提交于
TLS v1.2. These are sent as an extension for clients and during a certificate request for servers. TODO: add support for shared signature algorithms, respect shared algorithms when deciding which ciphersuites and certificates to permit.
-
- 18 6月, 2012 2 次提交
-
-
由 Dr. Stephen Henson 提交于
-
由 Dr. Stephen Henson 提交于
-
- 15 6月, 2012 1 次提交
-
-
由 Dr. Stephen Henson 提交于
for debugging purposes. Needs "enable-ssl-trace" configuration option.
-
- 11 6月, 2012 1 次提交
-
-
由 Ben Laurie 提交于
-
- 07 6月, 2012 1 次提交
-
-
由 Ben Laurie 提交于
-
- 06 6月, 2012 2 次提交
-
-
由 Ben Laurie 提交于
-
由 Ben Laurie 提交于
-
- 04 6月, 2012 1 次提交
-
-
由 Ben Laurie 提交于
-
- 30 5月, 2012 1 次提交
-
-
由 Ben Laurie 提交于
-
- 16 5月, 2012 1 次提交
-
-
由 Andy Polyakov 提交于
-
- 11 5月, 2012 3 次提交
-
-
由 Dr. Stephen Henson 提交于
Reported by: Phil Pennock <openssl-dev@spodhuis.org> Make renegotiation work for TLS 1.2, 1.1 by not using a lower record version client hello workaround if renegotiating.
-
由 Dr. Stephen Henson 提交于
Submitted by: PK <runningdoglackey@yahoo.com> Correct ciphersuite signature algorithm definitions.
-
由 Dr. Stephen Henson 提交于
DTLS to fix DoS attack. Thanks to Codenomicon for discovering this issue using Fuzz-o-Matic fuzzing as a service testing platform. (CVE-2012-2333)
-
- 27 4月, 2012 1 次提交
-
-
由 Dr. Stephen Henson 提交于
-
- 26 4月, 2012 2 次提交
-
-
由 Dr. Stephen Henson 提交于
OpenSSL 1.0.0. Add CHANGES entry noting the consequences.
-
由 Andy Polyakov 提交于
vector contiguous. PR: 2802
-
- 24 4月, 2012 3 次提交
-
-
由 Dr. Stephen Henson 提交于
Reviewed by: steve Improved localisation of TLS extension handling and code tidy.
-
由 Dr. Stephen Henson 提交于
-
由 Dr. Stephen Henson 提交于
-
- 19 4月, 2012 1 次提交
-
-
由 Dr. Stephen Henson 提交于
-
- 18 4月, 2012 1 次提交
-
-
由 Dr. Stephen Henson 提交于
-
- 17 4月, 2012 4 次提交
-
-
由 Bodo Möller 提交于
(TLS 1.2 clients could end up negotiating these with an OpenSSL server with TLS 1.2 disabled, which is problematic.) Submitted by: Adam Langley
-
由 Dr. Stephen Henson 提交于
If OPENSSL_MAX_TLS1_2_CIPHER_LENGTH is set then limit the size of client ciphersuites to this value. A value of 50 should be sufficient. Document workarounds in CHANGES.
-
由 Dr. Stephen Henson 提交于
Some servers hang when presented with a client hello record length exceeding 255 bytes but will work with longer client hellos if the TLS record version in client hello does not exceed TLS v1.0. Unfortunately this doesn't fix all cases...
-
由 Andy Polyakov 提交于
PR: 2791 Submitted by: Ben Noordhuis
-
- 16 4月, 2012 1 次提交
-
-
由 Andy Polyakov 提交于
PR: 2538
-
- 15 4月, 2012 1 次提交
-
-
由 Andy Polyakov 提交于
countermeasure. PR: 2778
-
- 12 4月, 2012 1 次提交
-
-
由 Dr. Stephen Henson 提交于
-