- Mar 09, 2016
-
-
Kurt Roeckx authored
Reviewed-by:Viktor Dukhovni <viktor@openssl.org> MR: #1595
-
Kurt Roeckx authored
Reviewed-by: -
Rob Percival authored
Reviewed-by:
Emilia Käsper <emilia@openssl.org> Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Rob Percival authored
Reviewed-by:
-
Rob Percival authored
Reviewed-by:
-
Rich Salz authored
Reviewed-by:Dr. Stephen Henson <steve@openssl.org>
-
Richard Levitte authored
The "extra checks" is a debugging tool to check the config resolving mechanism. It uses Perl's smart match, which is experimental and therefore always causes Perl to give out a warning, and it causes older Perl versions to fail entirely. So, it gets commented away, but stays otherwise in place, as it may be useful again. Reviewed-by:Matt Caswell <matt@openssl.org>
-
Richard Levitte authored
Reviewed-by: -
Richard Levitte authored
ct_test assumed it's run in the source directory and failed when built elsewhere. It still defaults to that, but can be told another story with the environment variables CT_DIR and CERTS_DIR. Test recipe updated to match. Reviewed-by:
-
Rob Percival authored
Reviewed-by:
-
Rob Percival authored
Reviewed-by:
-
Rob Percival authored
Reviewed-by:
-
Rob Percival authored
Both of these functions can easily be implemented by callers instead. Reviewed-by:
-
Rob Percival authored
Reviewed-by:
-
Rob Percival authored
Reviewed-by:
-
Rob Percival authored
Reviewed-by:
-
Rob Percival authored
Reviewed-by:
-
Rob Percival authored
Reviewed-by:
-
Rob Percival authored
Reviewed-by:
-
Rob Percival authored
Reviewed-by:
-
Rob Percival authored
Reviewed-by:
-
Rob Percival authored
Use "!x" instead of "x <= 0", as these functions never return a negative value. Reviewed-by:
-
Rob Percival authored
Reviewed-by:
-
Rob Percival authored
Also improves some documentation of those functions. Reviewed-by:
-
Rob Percival authored
No longer terminates on first error, but instead tries to set the source of every SCT regardless of whether an error occurs with some. Reviewed-by:
-
Todd Short authored
Properly check the return value of CRYPTO_THREAD_lock_new() Signed-off-by:
-
Richard Levitte authored
Reviewed-by: -
Richard Levitte authored
Reviewed-by: -
Richard Levitte authored
ct_test assumed it's run in the source directory and failed when built elsewhere. It still defaults to that, but can be told another story with the environment variables CT_DIR and CERTS_DIR. Test recipe updated to match. Reviewed-by: -
Matt Caswell authored
Update the CHANGES and NEWS files with information about the recently added AFALG engine and pipelining. Reviewed-by:Richard Levitte <levitte@openssl.org>
-
Matt Caswell authored
The Thread API changes broke classic build. This fixes it. Reviewed-by: -
Richard Levitte authored
If we find an IF within a clause that's skipped over, set it to be skipped as well. Reviewed-by: -
Matt Caswell authored
Reviewed-by: -
Matt Caswell authored
Reviewed-by: -
Matt Caswell authored
All OpenSSL code has now been transferred to use the new threading API, so the old one is no longer used and can be removed. We provide some compat macros for removed functions which are all no-ops. There is now no longer a need to set locking callbacks!! Reviewed-by: -
Matt Caswell authored
The locking here is a bit strange and unclear. Rather than refactor anything and possibly break stuff I have just moved to using the new thread API following as closely as possible what was there previously. Reviewed-by: -
Richard Levitte authored
Reviewed-by: -
Richard Levitte authored
Similarly, don't add e_capi if configured "no-capieng" Also, indent a little deeper, for clarity. Reviewed-by: -
Richard Levitte authored
Also, indent a little deeper, for clarity. Reviewed-by: -
Richard Levitte authored
Reviewed-by:
-
