- Dec 10, 2016
-
-
Dr. Stephen Henson authored
Reviewed-by:
Rich Salz <rsalz@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2065) (cherry picked from commit 71bbc79b) Conflicts: crypto/rsa/rsa_err.c include/openssl/rsa.h
-
- Dec 08, 2016
-
-
Richard Levitte authored
A bang (!) slipped through in the recent UI cleanup Reviewed-by:
-
Richard Levitte authored
Mostly condition check changes. Reviewed-by:
-
- Nov 29, 2016
-
-
Matt Caswell authored
Commit fa4c3745 got reverted, so this one also needs to be reverted as a result. This reverts commit ad69a303 . Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
- Nov 27, 2016
-
-
Vitezslav Cizek authored
Move rsa_key initialization in front of load_config(). If loading the config fails, rsa_key isn't initialized and may cause invalid free() in the end: cleanup. Remove superfluous memset. Reviewed-by:
Andy Polyakov <appro@openssl.org> Reviewed-by:
-
- Nov 26, 2016
-
-
Andy Polyakov authored
This is 1.0.2-specific reformat of 5ae5dc96 . Reviewed-by:
-
- Nov 25, 2016
-
-
Andy Polyakov authored
GH issue #1916 affects only big-endian platforms. TLS is not affected, because TLS fragment is never big enough. Reviewed-by:
Matt Caswell <matt@openssl.org> (cherry picked from commit 76f572ed)
-
- Nov 22, 2016
-
-
Richard Levitte authored
Reviewed-by:
-
- Nov 21, 2016
-
-
Kurt Roeckx authored
Backport of beacb0f0, revert of fa4c3745 Fixes: #1903 Reviewed-by:
-
- Nov 18, 2016
-
-
Beat Bolli authored
In the X509_NAME_get_index_by_NID.pod example, the initialized variable is called "loc", but the one used in the for loop is called "lastpos". Make the names match. CLA: trivial Reviewed-by:
-
- Nov 16, 2016
-
-
Orgad Shaneh authored
also on systems with makedepend that does not report its version, or that its version does not contain "gcc" or "clang". Some versions of makedepends just overwrite Makefile. Preserve the timestamp of the previous Makefile, and copy it back if it is unchanged. Reviewed-by:
-
Orgad Shaneh authored
... on systems with symlinks. Creating or overwriting a symlink sets the file ctime to the current time. This causes needless rebuilds because the time of all the headers is changed, and apparently make considers the link's time rather than the time of the target. Reviewed-by:
-
Orgad Shaneh authored
Reviewed-by:
-
Orgad Shaneh authored
... on systems without symlinks. Overwriting all the headers on each Configure causes full rebuild even if nothing has changed. Reviewed-by:
-
Orgad Shaneh authored
When Makefile/opensslconf.h is unchanged, don't write it at all. Currently every time Configure is executed, these files are overwritten. Makefile leads to regeneration of buildinf.h, and opensslconf.h is itself a central header. As a result, Configure triggers full rebuild, even if nothing is changed. Reviewed-by:
-
Rich Salz authored
Factorise multiple bn_get_top(group->field) calls Add missing checks on some conditional BN_copy return value Add missing checks on some BN_copy return value Add missing checks on a few bn_wexpand return value Reviewed-by:
-
- Nov 13, 2016
-
-
Matthias Kraft authored
Avoid a memory alignment issue. Signed-off-by:
Matthias Kraft <Matthias.Kraft@softwareag.com> CLA: trivial Reviewed-by:
-
- Nov 10, 2016
-
-
Matt Caswell authored
Reviewed-by: -
Andy Polyakov authored
Reviewed-by:
-
- Nov 08, 2016
-
-
Andy Polyakov authored
Build failure was reported in GH#1818 if APPS environment was defined. Reviewed-by:
Tim Hudson <tjh@openssl.org> (Merged from https://github.com/openssl/openssl/pull/1864)
-
- Nov 04, 2016
-
-
Rich Salz authored
Reviewed-by:
-
- Nov 02, 2016
-
-
Matt Caswell authored
Reviewed-by: -
Matt Caswell authored
TLS1.0 and TLS1.1 say you SHOULD ignore unrecognised record types, but TLS 1.2 says you MUST send an unexpected message alert. We swap to the TLS 1.2 behaviour for all protocol versions to prevent issues where no progress is being made and the peer continually sends unrecognised record types, using up resources processing them. Issue reported by 郭志攀 Reviewed-by: -
Matt Caswell authored
The heartbeat_test reaches into the internals of libssl and calls some internal functions. It then checks the return value to check its what it expected. However commit fa4c3745 changed the return value of these internal functions, and now the test is failing. The solution is to update the test to look for the new return value. Reviewed-by:
-
Richard Levitte authored
Forks will have to define their own Reviewed-by:
-
- Nov 01, 2016
-
-
Benjamin Kaduk authored
Reviewed-by:
-
- Oct 28, 2016
-
-
Richard Levitte authored
Without this, any linker flag the user gave when configuring are ignored. Reviewed-by:
-
Matt Caswell authored
Replace the various length checks in the extension code with a macro to simplify the logic. Reviewed-by: -
Matt Caswell authored
The previous commit inspired a review of all the length checks for the extension adding code. This adds more robust checks and adds checks where some were missing previously. The real solution for this is to use WPACKET which is currently in master - but that cannot be applied to release branches. Reviewed-by: -
Matt Caswell authored
The status request extension did not correctly check its length, meaning that writing the extension could go 2 bytes beyond the buffer size. In practice this makes little difference because, due to logic in buffer.c the buffer is actually over allocated by approximately 5k! Issue reported by Guido Vranken. Reviewed-by: -
Matt Caswell authored
Providing a spkac file with no default section causes a double free. Thanks to Brian Carpenter for reporting this issue. Reviewed-by:
Kurt Roeckx <kurt@openssl.org> (cherry picked from commit 229bd124)
-
Matt Caswell authored
A zero return from BIO_read()/BIO_write() could mean that an IO operation is retryable. A zero return from SSL_read()/SSL_write() means that the connection has been closed down (either cleanly or not). Therefore we should not propagate a zero return value from BIO_read()/BIO_write() back up the stack to SSL_read()/SSL_write(). This could result in a retryable failure being treated as fatal. Reviewed-by:
-
- Oct 26, 2016
-
-
Rich Salz authored
Reviewed-by:
-
- Oct 25, 2016
-
-
Dr. Matthias St. Pierre authored
A temporary buffer containing g^xy was not cleared in ecdh_compute_key() before freeing it, so the shared secret was leaked in memory. Reviewed-by:
-
- Oct 22, 2016
-
-
Rich Salz authored
Unhandled critical CRL extensions were not detected if they appeared after the handled ones. (GitHub issue 1757). Thanks to John Chuah for reporting this. Reviewed-by:
-
- Oct 20, 2016
-
-
Cristian Stoica authored
The structure has already been initialized to zero with memset. See also commit 64b25758 (remove 0 assignments) Signed-off-by:
Cristian Stoica <cristian.stoica@nxp.com> CLA: trivial Reviewed-by:
-
Richard Levitte authored
This avoids failures when configuring with --strict-warnings Reviewed-by:
-
Richard Levitte authored
This removes some #ifndef clutter. Reviewed-by:
-
Richard Levitte authored
In apps/apps.c, one can set up an engine with setup_engine(). However, we freed the structural reference immediately, which means that for engines that don't already have a structural reference somewhere else (because it has registered at least one cipher or digest algorithm method, and therefore gets a functional reference through the ENGINE_set_default() call), we end up returning an invalid reference. Instead, the function release_engine() is added, and called at the end of the routines that call setup_engine(). Originally, the ENGINE API wasn't designed for this to happen, an engine had to register at least one algorithm method, and was especially expected to register the algorithms corresponding to the key types that could be stored and hidden in hardware. However, it turns out that some engines will not register those algorithms with the ENGINE_set_{algo}, ENGINE_set_cipher or ENGINE_set_digest functions, as they only want the methods to be used for keys, not as general crypto accelerator methods. That may cause ENGINE_set_default() to do nothing, and no functional reference is therefore made, leading to a premature deallocation of the engine and it thereby becoming unavailable when trying to fetch a key. Reviewed-by:
-
- Oct 19, 2016
-
-
Richard Levitte authored
Reviewed-by:
-
