In 0.9.8za, there is a missing compiler directive to
include limits.h in ssl/s3_pkt.c. Without it, compiling
fails on SPARC Solaris 10 with INT_MAX being undefined on
line 536, which looks like:
OPENSSL_assert(s->s3->wnum < INT_MAX);
It appears that 1.0.0m has the same problem. I haven't l
On 6/5/2014 11:31 PM, Green, Gatewood wrote:
Openssl-0.9.8za will not build in FIPS mode. The openssl-fips-1.2(.4) seems to
be missing the symbol BN_consttime_swap.
By the way, the BN_consttime_swap implementation in 1.0.1g (still
downloading 1.0.1h) doesn't seem to completely match its
descr
On 06/06/2014 04:12 AM, Salz, Rich wrote:
Does that mean this RCE is a heap based overflow?
I/O buffers in openssl are generally (always?) from the heap, not on the stack.
The DTLS code uses on-stack buffers for discarding packets, but those
read calls are not affected by the present issue.
On 27 May 2014 08:00, Anant Rao wrote:
> When I tried to decrypt it using OpenSSL in a 'c' program, the last call
> 'EVP_DecryptFinal_ex' fails. Somehow, ERR_print_errors_fp is not printing
> anything either.
If EVP_DecryptFinal_ex fails with GCM then this means that the tag has
failed to verify
On 2014-06-05, Jeffrey Walton wrote:
> CVE-2014-0195 is a buffer overflow
> (https://www.openssl.org/news/secadv_20140605.txt):
By the way, this one is currently missing from the list on
http://www.openssl.org/news/vulnerabilities.html.
___
Hi,
I only used the CCM example that contains the same comment at the
comparable point in its code.
If I remember correctly this comment means that no data will be added
to outbuf. Hence, outlen should be 0. I have not stepped through the
code, but that seems to be meaningful as CCM and GCM use c
The redhat podcast with Mark (Cox) probably answers this best;
http://bit.ly/Th64oP
On Thu, Jun 5, 2014 at 12:04 PM, Juha Saarinen wrote:
> Hi Steve,
>
> That’s quite a few in one go - is this due to greater testing of OpenSSL
> and more scrutiny of the code by the community?
>
> Of the flaws
