- 15 7月, 2012 2 次提交
-
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
-
- 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 4 次提交
-
-
由 Richard Levitte 提交于
-
由 Richard Levitte 提交于
-
由 Richard Levitte 提交于
-
由 Richard Levitte 提交于
Add aliases for SSL_CTX_set_not_resumable_session_callback and SSL_set_not_resumable_session_callback on top of that.
-
- 04 7月, 2012 3 次提交
-
-
由 Dr. Stephen Henson 提交于
-
由 Dr. Stephen Henson 提交于
Reported by: David McCullough <david_mccullough@mcafee.com> Restore fips configuration module from 0.9.8.
-
由 Dr. Stephen Henson 提交于
Always perform nexproto callback argument initialisation in s_server otherwise we use uninitialised data if -nocert is specified.
-
- 03 7月, 2012 5 次提交
-
-
由 Dr. Stephen Henson 提交于
-
由 Dr. Stephen Henson 提交于
-
由 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.
-
- 02 7月, 2012 5 次提交
-
-
由 Andy Polyakov 提交于
PR: 2837
-
由 Andy Polyakov 提交于
-
由 Dr. Stephen Henson 提交于
-
由 Dr. Stephen Henson 提交于
-
由 Dr. Stephen Henson 提交于
-
- 01 7月, 2012 2 次提交
-
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
-
- 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 2 次提交
-
-
由 Dr. Stephen Henson 提交于
-
由 Andy Polyakov 提交于
path with spaces. PR: 2835
-
- 26 6月, 2012 1 次提交
-
-
由 Andy Polyakov 提交于
-
- 25 6月, 2012 2 次提交
-
-
由 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.
-
由 Andy Polyakov 提交于
-
- 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.
-
- 19 6月, 2012 3 次提交
-
-
由 Dr. Stephen Henson 提交于
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
-
- 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.
-
- 13 6月, 2012 1 次提交
-
-
由 Dr. Stephen Henson 提交于
-
- 12 6月, 2012 2 次提交
-
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
-