- 29 8月, 2014 4 次提交
-
-
由 Dr. Stephen Henson 提交于
Use "parse" and "add" for function and callback names instead of "first" and "second". Change arguments to callback so the extension type is unsigned int and the buffer length is size_t. Note: this *will* break existing code. Reviewed-by: NEmilia Käsper <emilia@openssl.org>
-
由 Dr. Stephen Henson 提交于
Since sanity checks are performed for all custom extensions the serverinfo checks are no longer needed. Reviewed-by: NEmilia Käsper <emilia@openssl.org>
-
由 Dr. Stephen Henson 提交于
Reject attempts to use extensions handled internally. Add flags to each extension structure to indicate if an extension has been sent or received. Enforce RFC5246 compliance by rejecting duplicate extensions and unsolicited extensions and only send a server extension if we have sent the corresponding client extension. Reviewed-by: NEmilia Käsper <emilia@openssl.org>
-
由 Dr. Stephen Henson 提交于
Use the same structure for client and server custom extensions. Add utility functions in new file t1_ext.c. Use new utility functions to handle custom server and client extensions and remove a lot of code duplication. Reviewed-by: NEmilia Käsper <emilia@openssl.org>
-
- 28 8月, 2014 1 次提交
-
-
由 Emilia Kasper 提交于
Pull constant-time methods out to a separate header, add tests. Reviewed-by: NBodo Moeller <bodo@openssl.org>
-
- 22 8月, 2014 1 次提交
-
-
由 Emilia Kasper 提交于
Use existing error code SSL_R_RECORD_TOO_SMALL for too many empty records. For ease of backporting the patch to release branches. Reviewed-by: NBodo Moeller <bodo@openssl.org>
-
- 20 8月, 2014 1 次提交
-
-
由 Martin Olsson 提交于
Don't need to check auth for NULL since we did when we assigned to it. Reviewed-by: NEmilia Kasper <emilia@openssl.org>
-
- 19 8月, 2014 1 次提交
-
-
由 John Fitzgibbon 提交于
Extra SSL_get_selected_srtp_profile() declaration in ssl/srtp.h causes -Werror builds to fail. Reviewed-by: NTim Hudson <tjh@openssl.org>
-
- 18 8月, 2014 1 次提交
-
-
由 Justin Blanchard 提交于
Add a dozen more const declarations where appropriate. These are from Justin; while adding his patch, I noticed ASN1_BIT_STRING_check could be fixed, too. Reviewed-by: NDr. Stephen Henson <steve@openssl.org>
-
- 16 8月, 2014 2 次提交
-
-
由 Hubert Kario 提交于
While RFC6367 focuses on Camellia-GCM cipher suites, it also adds a few cipher suites that use SHA-2 based HMAC that can be very easily added. Tested against gnutls 3.3.5 PR#3443 Reviewed-by: NTim Hudson <tjh@openssl.org>
-
由 Matt Caswell 提交于
PR#3450 Reviewed-by: NEmilia Käsper <emilia@openssl.org>
-
- 15 8月, 2014 3 次提交
-
-
由 Hans Wennborg 提交于
Remove some redundant logical expressions Reviewed-by: NEmilia Kasper <emilia@silkandcyanide.net>
-
由 Dr. Stephen Henson 提交于
Move custom extension structures from SSL_CTX to CERT structure. This change means the form can be revised in future without binary compatibility issues. Also since CERT is part of SSL structures so per-SSL custom extensions could be supported in future as well as per SSL_CTX. Reviewed-by: NRich Salz <rsalz@openssl.org> Reviewed-by: NEmilia Käsper <emilia@openssl.org>
-
由 Dr. Stephen Henson 提交于
Reviewed-by: NEmilia Käsper <emilia@openssl.org>
-
- 14 8月, 2014 1 次提交
-
-
由 Emilia Kasper 提交于
Reviewed-by: NDr. Stephen Henson <steve@openssl.org>
-
- 09 8月, 2014 3 次提交
-
-
由 Dr. Stephen Henson 提交于
The addition of SRP authentication needs to be checked in various places to work properly. Specifically: A certificate is not sent. A certificate request must not be sent. Server key exchange message must not contain a signature. If appropriate SRP authentication ciphersuites should be chosen. Reviewed-by: NMatt Caswell <matt@openssl.org>
-
由 Viktor Szakats 提交于
The "unsigned char *d" should be const. Reviewed-by: NKurt Roeckx <kurt@roeckx.be>
-
由 Matthieu Crapet 提交于
Use SSL3_AL_FATAL instead of the literal constant "2" Every bit of cleanup helps. Reviewed-by: NMatt Caswell <matt@openssl.org>
-
- 07 8月, 2014 12 次提交
-
-
由 Dr. Stephen Henson 提交于
Check SRP parameters when they are received so we can send back an appropriate alert. Reviewed-by: NKurt Roeckx <kurt@openssl.org>
-
由 Dr. Stephen Henson 提交于
If a client attempted to use an SRP ciphersuite and it had not been set up correctly it would crash with a null pointer read. A malicious server could exploit this in a DoS attack. Thanks to Joonas Kuorilehto and Riku Hietamäki from Codenomicon for reporting this issue. CVE-2014-2970 Reviewed-by: NTim Hudson <tjh@openssl.org>
-
由 Gabor Tyukasz 提交于
CVE-2014-3509 Reviewed-by: NTim Hudson <tjh@openssl.org> Reviewed-by: NDr. Stephen Henson <steve@openssl.org>
-
由 Emilia Käsper 提交于
CVE-2014-3510 Reviewed-by: NDr. Stephen Henson <steve@openssl.org>
-
由 David Benjamin 提交于
CVE-2014-3511 Reviewed-by: NEmilia Käsper <emilia@openssl.org> Reviewed-by: NBodo Möller <bodo@openssl.org>
-
由 Adam Langley 提交于
In a couple of functions, a sequence number would be calculated twice. Additionally, in |dtls1_process_out_of_seq_message|, we know that |frag_len| <= |msg_hdr->msg_len| so the later tests for |frag_len < msg_hdr->msg_len| can be more clearly written as |frag_len != msg_hdr->msg_len|, since that's the only remaining case. Reviewed-by: NMatt Caswell <matt@openssl.org> Reviewed-by: NEmilia Käsper <emilia@openssl.org>
-
由 Matt Caswell 提交于
Applying same fix as in dtls1_process_out_of_seq_message. A truncated DTLS fragment would cause *ok to be clear, but the return value would still be the number of bytes read. Problem identified by Emilia Käsper, based on previous issue/patch by Adam Langley. Reviewed-by: NEmilia Käsper <emilia@openssl.org>
-
由 Adam Langley 提交于
Previously, a truncated DTLS fragment in |dtls1_process_out_of_seq_message| would cause *ok to be cleared, but the return value would still be the number of bytes read. This would cause |dtls1_get_message| not to consider it an error and it would continue processing as normal until the calling function noticed that *ok was zero. I can't see an exploit here because |dtls1_get_message| uses |s->init_num| as the length, which will always be zero from what I can see. Reviewed-by: NMatt Caswell <matt@openssl.org> Reviewed-by: NEmilia Käsper <emilia@openssl.org>
-
由 Adam Langley 提交于
The |pqueue_insert| function can fail if one attempts to insert a duplicate sequence number. When handling a fragment of an out of sequence message, |dtls1_process_out_of_seq_message| would not call |dtls1_reassemble_fragment| if the fragment's length was zero. It would then allocate a fresh fragment and attempt to insert it, but ignore the return value, leaking the fragment. This allows an attacker to exhaust the memory of a DTLS peer. Fixes CVE-2014-3507 Reviewed-by: NMatt Caswell <matt@openssl.org> Reviewed-by: NEmilia Käsper <emilia@openssl.org>
-
由 Matt Caswell 提交于
In |dtls1_reassemble_fragment|, the value of |msg_hdr->frag_off+frag_len| was being checked against the maximum handshake message size, but then |msg_len| bytes were allocated for the fragment buffer. This means that so long as the fragment was within the allowed size, the pending handshake message could consume 16MB + 2MB (for the reassembly bitmap). Approx 10 outstanding handshake messages are allowed, meaning that an attacker could consume ~180MB per DTLS connection. In the non-fragmented path (in |dtls1_process_out_of_seq_message|), no check was applied. Fixes CVE-2014-3506 Wholly based on patch by Adam Langley with one minor amendment. Reviewed-by: NEmilia Käsper <emilia@openssl.org>
-
由 Matt Caswell 提交于
Reviewed-by: NEmilia Käsper <emilia@openssl.org>
-
由 Adam Langley 提交于
The |item| variable, in both of these cases, may contain a pointer to a |pitem| structure within |s->d1->buffered_messages|. It was being freed in the error case while still being in |buffered_messages|. When the error later caused the |SSL*| to be destroyed, the item would be double freed. Thanks to Wah-Teh Chang for spotting that the fix in 1632ef74 was inconsistent with the other error paths (but correct). Fixes CVE-2014-3505 Reviewed-by: NMatt Caswell <matt@openssl.org> Reviewed-by: NEmilia Käsper <emilia@openssl.org>
-
- 25 7月, 2014 1 次提交
-
-
由 Dr. Stephen Henson 提交于
Don't call internal functions directly call them through SSL_test_functions(). This also makes unit testing work on Windows and platforms that don't export internal functions from shared libraries. By default unit testing is not enabled: it requires the compile time option "enable-unit-test". Reviewed-by: NGeoff Thorpe <geoff@openssl.org>
-
- 20 7月, 2014 2 次提交
-
-
由 Mike Bland 提交于
ssl/ssl_locl.h now comes first to ensure that it will compile standalone. test/testutil.h is considered to be in the same directory as the test file, since the test file will be linked into test/ and built there. Reviewed-by: NTim Hudson <tjh@openssl.org>
-
由 Mike Bland 提交于
Reviewed-by: NTim Hudson <tjh@openssl.org>
-
- 16 7月, 2014 1 次提交
-
-
由 Dr. Stephen Henson 提交于
Use same logic when determining when to expect a client certificate for both TLS and DTLS. PR#3452
-
- 15 7月, 2014 1 次提交
-
-
由 Dr. Stephen Henson 提交于
-
- 14 7月, 2014 1 次提交
-
-
由 Peter Mosmans 提交于
PR#3440
-
- 09 7月, 2014 1 次提交
-
-
由 Andy Polyakov 提交于
PR: #3424,#3423,#3422
-
- 06 7月, 2014 1 次提交
-
-
由 Andy Polyakov 提交于
-
- 05 7月, 2014 2 次提交
-
-
由 Ben Laurie 提交于
-
由 Dr. Stephen Henson 提交于
PR#319 (reoponed version).
-