openssl/crypto, branch OpenSSL_1_0_2j

Prepare for 1.0.2j release

2016-09-26T09:49:49Z

Reviewed-by: Richard Levitte

Add some sanity checks when checking CRL scores

2016-09-26T08:19:50Z

Note: this was accidentally omitted from OpenSSL 1.0.2 branch. Without this fix any attempt to use CRLs will crash. CVE-2016-7052 Thanks to Bruce Stephens and Thomas Jakobi for reporting this issue. Reviewed-by: Stephen Henson Reviewed-by: Rich Salz

Fix typo introduced by a03f81f4

2016-09-22T12:57:09Z

Reviewed-by: Richard Levitte

Prepare for 1.0.2j-dev

2016-09-22T10:25:49Z

Reviewed-by: Richard Levitte

Prepare for 1.0.2i release

2016-09-22T10:24:53Z

Reviewed-by: Richard Levitte

GH1555: Don't bump size on realloc failure

2016-09-21T14:42:10Z

Reviewed-by: Richard Levitte (cherry picked from commit 6fcace45bda108ad4d3f95261494dd479720d92c)

Fix a missing NULL check in dsa_builtin_paramgen

2016-09-21T12:35:11Z

We should check the last BN_CTX_get() call to ensure that it isn't NULL before we try and use any of the allocated BIGNUMs. Issue reported by Shi Lei. Reviewed-by: Richard Levitte (cherry picked from commit 1ff7425d6130380bb00d3e64739633a4b21b11a3)

initialize the RSA struct to 0.

2016-09-20T02:06:35Z

This helps with program code linked against static builds accessing a uninitialized ->engine pointer. CLA: none; trivial Reviewed-by: Tim Hudson Reviewed-by: Rich Salz (Merged from https://github.com/openssl/openssl/pull/1540)

VMS: only use _realloc32 with /POINTER_SIZE=32

2016-09-15T08:33:42Z

This fixes the following error when building with no particular pointer size is specified (implied 32 bit): static void *(*realloc_func) (void *, size_t) = realloc; ................................................^ %CC-E-UNDECLARED, In the initializer for realloc_func, "_realloc32" is not declared. at line number 93 in file DEV:[OPENSSL102.crypto]mem.c;1 Reviewed-by: Andy Polyakov

Add some sanity checks around usage of t_fromb64()

2016-09-14T09:17:46Z

The internal SRP function t_fromb64() converts from base64 to binary. It does not validate that the size of the destination is sufficiently large - that is up to the callers. In some places there was such a check, but not in others. Add an argument to t_fromb64() to provide the size of the destination buffer and validate that we don't write too much data. Also add some sanity checks to the callers where appropriate. With thanks to Shi Lei for reporting this issue. Reviewed-by: Richard Levitte (cherry picked from commit 73f0df8331910d6726d45ecaab12bd93cc48b4e2)