Hi David and thank you for your advice and example.
I tried to compile it, run onto errors tough.
I just put the file into my openssl source tree, which is on commit:
commit 9e86b3815719d29f7bde2294403f97c42ce82a16 (HEAD,
origin/openssl-3.0)
Author: Randall S. Becker
Date: Tue Jun 14 06:10:5
My guess is that the loop is caused by one of the commits 0ed27fb7a8 and
8438d3a7b7.
Would you mind to (a) check whether that's correct and which one of the two
commits
causes the problem, and (b) raise a GitHub issue for it?
Matthias
~/src/openssl/1.1.1$ git log --oneline --stat OpenSSL_1_1_
On June 21, 2022 7:40 PM, I wrote:
>Our test process for 10-test_bn went into a hard loop when building using
IEEE
>float. This has not happened in prior tests or when using platform floating
point
>(default). The situation does not occur in 3.0.4 - only 1.1.1p. At 1.1.1o
there was no
>issue. I am
I am trying to build the 1.1.1p and 3.0.4 versions of OpenSSL. Each
version now fails in the same place (test/v3ext.c). The error is about
undefined ASIdentifiers, etc. in the newly added test_asid() function.
It looks like the newly added test_asid() function needs an '#ifndef
OPENSSL_NO_RF
Our test process for 10-test_bn went into a hard loop when building using
IEEE float. This has not happened in prior tests or when using platform
floating point (default). The situation does not occur in 3.0.4 - only
1.1.1p. At 1.1.1o there was no issue. I am concerned that there are
assumptions ma
longer receiving updates of any kind.
The impact of these issues on OpenSSL 1.1.0 has not been analysed.
Users of these versions should upgrade to OpenSSL 3.0 or 1.1.1.
References
==
URL for this Security Advisory:
https://www.openssl.org/news/secadv/20220621.txt
Note: the online version of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0.4 released
==
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 3.0.4 of our open source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 1.1.1p released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 1.1.1p of our open sour
On 21/06/2022 11:42, Tomas Mraz wrote:
This is actually not a memory allocated by the SSL_CTX_new() itself but
error string data that is global. There is no real memory leak here.
You can call OPENSSL_cleanup() to explicitly de-allocate all the global
data however please note that you can do
On 16/06/2022 05:52, Ramaiah, Ravichandran Bagalur wrote:
*SSL error (78c0100): malloc failure
Do you get anything in the OpenSSL error stack for this (e.g. try
"ERR_print_errors_fp(stdout);").
We need a bit more to go on to figure out where specifically the malloc
failure is occurring.
On Tue, 2022-06-21 at 10:33 +, Tiwari, Hari Sahaya wrote:
> Hi,
> I need one clarification on routine SSL_CTX_free(). I see the memory
> is not freed even after calling this SSL_CTX_free().
>
> I have a simple test program, which just does SSL_CTX_new() and
> SSL_CTX_free().
>
> #include
>
Hi,
I need one clarification on routine SSL_CTX_free(). I see the memory is not
freed even after calling this SSL_CTX_free().
I have a simple test program, which just does SSL_CTX_new() and SSL_CTX_free().
#include
#include
int main()
{
const SSL_METHOD *method;
SSL_CTX *ctx = NULL;
Hi All,
Could anyone tell me if this issue is caused due to application error or an
openssl bug?
This malloc failure is happening when I try to establish TLS connection between
2 SIP applications.
Regards,
Ravi
From: Ramaiah, Ravichandran Bagalur
Sent: Thursday, June 16, 2022 10:23 AM
To: ope
On 20/06/2022 22:29, Rouzier, James wrote:
Hi Matt,
What would it take to expose this?
At the moment you can serialize an SSL_SESSION object - but this only
helps during session resumption. So, using this capability, you could
perform a resumption handshake on a different server to where
14 matches
Mail list logo
