- 12 Mar, 2016 6 commits
-
-
Emilia Kasper authored
ccache + clang produces a false strcmp warning, see https://llvm.org/bugs/show_bug.cgi?id=20144 Since this only happens with ccache and --strict-warnings, and only with certain versions of glibc / clang, disabling ccache is a reasonable short-term workaround. Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Emilia Kasper authored
Reviewed-by:
Matt Caswell <matt@openssl.org>
-
Rich Salz authored
Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Richard Levitte authored
While insignificant on Unix like systems, this is significant on systems like VMS. Reviewed-by:
Rich Salz <rsalz@openssl.org> Reviewed-by:
Tim Hudson <tjh@openssl.org>
-
Richard Levitte authored
It turns out that different sed implementations treat -i differently to cause issues. make it simpler by avoiding it entirely and give perl the trust to be consistent enough. Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
That doesn't change even to make a dummy to hide its unavailability. Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
- 11 Mar, 2016 26 commits
-
-
Matt Caswell authored
Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Matt Caswell authored
On Windows we call WSAGetLastError() to find out the last error that happened on a socket operation. We use this to find out whether we can retry the operation or not. You are supposed to call this immediately however in a couple of places we logged an error first. This can end up making other Windows system calls to get the thread local error state. Sometimes that can clobber the error code, so if you call WSAGetLastError() later on you get a spurious response and the socket operation looks like a fatal error. Really we shouldn't be logging an error anyway if its a retryable issue. Otherwise we could end up with stale errors on the error queue. Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Mat authored
verified that build succeeds without the extra define Reviewed-by:
Richard Levitte <levitte@openssl.org> Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Mat authored
Fix no-blake2 for Windows classic build Reviewed-by:
Richard Levitte <levitte@openssl.org> Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Dr. Stephen Henson authored
Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Dr. Stephen Henson authored
Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
The issue is demonstrated as follows: On Linux: $ echo ': foo.h /usr/include/stddef.h bar.h' | sed -e 's/ \/\(\\.\|[^ ]\)*//g' : foo.h bar.h On MacOS X: $ echo ': foo.h /usr/include/stddef.h bar.h' | sed -e 's/ \/\(\\.\|[^ ]\)*//g' : foo.husr/include/stddef.h bar.h Perl is more consistent: On Linux: $ echo ': foo.h /usr/include/stddef.h bar.h' | perl -pe 's/ \/(\\.|[^ ])*//g;' : foo.h bar.h On MacOS X: $ echo ': foo.h /usr/include/stddef.h bar.h' | perl -pe 's/ \/(\\.|[^ ])*//g;' : foo.h bar.h Reviewed-by:
Andy Polyakov <appro@openssl.org>
-
Rich Salz authored
Reviewed-by:
Emilia Käsper <emilia@openssl.org>
-
Kurt Roeckx authored
Reviewed-by:
Andy Polyakov <appro@openssl.org> Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Kurt Roeckx authored
They are not numbers in the machine byte order. Reviewed-by:
Andy Polyakov <appro@openssl.org> Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Kurt Roeckx authored
Reviewed-by:
Andy Polyakov <appro@openssl.org> Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Bill Cox authored
Reviewed-by:
Andy Polyakov <appro@openssl.org> Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Dr. Stephen Henson authored
Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Andy Polyakov authored
Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Andy Polyakov authored
Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Andy Polyakov authored
If pre-processor failed, an empty .s file could be left behind, which could get successfully compiled if one simply re-ran make and cause linking failures. Not anymore. Remove even intermediate .S in case of pre-processor failure. Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Andy Polyakov authored
Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Rob Percival authored
Reviewed-by:
Emilia Käsper <emilia@openssl.org> Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Rob Percival authored
Reviewed-by:
Emilia Käsper <emilia@openssl.org> Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Matt Caswell authored
Running test_ssl with HARNESS_VERBOSE results in lots of spurious warnings about an inability to load the CT config file. This fixes it. Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Richard Levitte authored
Issue identified on Solaris by Erik Forsberg <erik@efca.com> Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Matt Caswell authored
During auto de-init we were calling ENGINE_cleanup(), and then later CONF_modules_free(). However the latter function can end up calling engine code, which can lead to a use of the global_engine_lock after it has already been freed. Therefore we should swap the calling order of these two functions. Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Mat authored
no-ripemd was unified a while ago but the change was not done in mk1mf.pl. This commit changes the no-ripemd string to no-rmd160 which fixes the no-rmd160 classic build. Reviewed-by:
Rich Salz <rsalz@openssl.org> Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Richard Levitte authored
Experience has shown that dynamic engines with their own copy of libcrypto is problematic, so we disable that possibility. Reviewed-by:
Matt Caswell <matt@openssl.org>
-
Richard Levitte authored
One of them didn't clean away .d.tmp files properly. The other would overwrite the .d files unconditionally, thereby causing a possibly unnecessary dependency rebuild, which touches the date of Makefile, which causes a possibly unnecessary rebuild of buildinf.h and everything that depends on that. Reviewed-by:
Andy Polyakov <appro@openssl.org>
-
Matt Caswell authored
A few things were out of date and a few things were missing. Also some formatting updates. Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
- 10 Mar, 2016 8 commits
-
-
Richard Levitte authored
Some of these scripts would recognise an output parameter if it looks like a file path. That works both in both the classic and new build schemes. Some fo these scripts would only recognise it if it's a basename (i.e. no directory component). Those need to be corrected, as the output parameter in the new build scheme is more likely to contain a directory component than not. Reviewed-by:
Andy Polyakov <appro@openssl.org>
-
Richard Levitte authored
A few were missed in the previous commit. Closes RT#4412 Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Rob Percival authored
Use SSL_get_SSL_CTX instead of passing SSL_CTX to s_client.c:print_stuff Reviewed-by:
Emilia Käsper <emilia@openssl.org> Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Rob Percival authored
Pass entire CTLOG_STORE to SCT_print, rather than just the SCT's CTLOG SCT_print now looks up the correct CT log for you. Reviewed-by:
Emilia Käsper <emilia@openssl.org> Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Rob Percival authored
Remove 'log' field from SCT and related accessors In order to still have access to an SCT's CTLOG when calling SCT_print, SSL_CTX_get0_ctlog_store has been added. Improved documentation for some CT functions in openssl/ssl.h. Reviewed-by:
Emilia Käsper <emilia@openssl.org> Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
Closes RT#4406 Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
Reviewed-by:
Stephen Henson <steve@openssl.org>
-
Richard Levitte authored
Reviewed-by:
Stephen Henson <steve@openssl.org>
-