On 17/10/2022 13:10, Ashok Kumar Sarode via openssl-users wrote:
NOTE: I have re-named file openssl\*configuration.h.in* to
openssl\*configuration.h*
Likewise i re-named err.h, ssl.h, opensslv.h, crypto.h
Don't do that. That is almost certainly the cause of these errors. The
"
Hello OpenSSL users,
I need help on following errors which I am getting from myWindows machine
building on Visual Studio 2019,
Version 16.11.17.
Build started...1>-- Build started: Project: executeHelloWorld,
Configuration: Debug Win32
--1>VerifyJWTSignUsingRSA.cpp1>C:\Us
Tested on a separate machine (Ubuntu Jammy Jellyfish) that comes with
OpenSSL 3.x installed and things worked as expected.
Probably something was screwed with my own build or the machine that has
several OpenSSL versions.
Thanks for the help, and sorry for the inconvenience.
Cheers,
Jose
On
On 30/11/2021 13:16, pepone.onrez wrote:
Getting some problems with OpenSSL 3.0, I have passwordError function,
to check if the last error was due to an invalid password and allow the
user to retry.
bool
passwordError()
{
unsigned long error = ERR_peek_error();
unsigned long lib
Getting some problems with OpenSSL 3.0, I have passwordError function, to
check if the last error was due to an invalid password and allow the user
to retry.
bool
passwordError()
{
unsigned long error = ERR_peek_error();
unsigned long lib = ERR_GET_LIB(error);
unsigned long reason =
Subject: Re: Establishing connection errors
Sorry, accidentally skipped that part, which was sort of important. I think I
can use the same fix because the part I skipped is the problem:
X509 *cert;
cert = PEM_read_X509(fp, NULL, 0, NULL);
status = X509_STORE_add_cert(trusted_store,cert);
So
: Establishing connection errors
On Fri, 2021-11-05 at 13:48 +, Jason Schultz wrote:
> For setting up the trusted store, when the application starts, it
> calls:
>
> ssl_trusted_certs = X509_STORE_new()
>
> ...and then reads all of the certificates in /etc/ssl/certs/ calling
>
On Fri, 2021-11-05 at 13:48 +, Jason Schultz wrote:
> For setting up the trusted store, when the application starts, it
> calls:
>
> ssl_trusted_certs = X509_STORE_new()
>
> ...and then reads all of the certificates in /etc/ssl/certs/ calling
> X509_STORE_add_cert(trusted_store,cert);
>
equence applications depending on
# OpenSSL may not work correctly which could lead to significant system
# problems including inability to remotely access the system.
[default_sect]
# activate = 1
[base_sect]
activate = 1
And in fipsmodule.cnf:
[fips_sect]
activate = 1
conditional-errors = 1
security-che
On Fri, 2021-11-05 at 13:04 +, Jason Schultz wrote:
> I know I've been raising a lot of issues this week, because of
> varying reasons, but I've hit another one that seems like either an
> OpenSSL problem, or something new/different I need to do with OpenSSL
> 3.0 in connection establishment.
routines::decode error
211105074132.795:SSL_process_hs: SSL_ERROR_SSL ERR_get_error error string:
error:0580006C:x509 certificate routines::unable to get certs public key
Some of those errors are pretty generic, but when searching the 3.0 source for
the "unable to get certs public key&q
Please reply to the list rather than to me directly.
> From: Kamala Ayyar
> Sent: Thursday, 26 August, 2021 08:57
> We call the WSAGetLastError immediately after SSL_ERROR_SYSCALL and we get
> the
> WSAETIMEDOUT
OK. This wasn't entirely clear to me from your previous message. So you are
> From: Kamala Ayyar
> Sent: Monday, 23 August, 2021 09:22
> We get the SSL_ERROR_SYSCALL from SSL_Read and SSL_Write quite often.
You'll get SSL_ERROR_SYSCALL any time OpenSSL makes a system call (including,
on Windows, a Winsock call) and gets an error.
> It seems the handshake is done
use to a non-blocking socket due
to platform and application limitation
Enjoy
Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S. https://www.wisemo.com
Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo
ressing a symptom rather
> than the underlying problem.
>
> > . We are trying to find why we get the SSL_Read/SSL_Write Error as it a
> Blocking
> > socket. We cannot use to a non-blocking socket due to platform and
> application
> > limitation
>
> You said you're specifical
ifically getting SSL_ERROR_SYSCALL from SSL_read and
SSL_write. That has nothing to do with whether the socket is in blocking mode
-- system calls on blocking sockets can certainly return errors. I don't
understand this question.
There are any number of reasons why the server's ability to hand
* We have a server that has around 2025 clients connected at any instant.
* Our application creates a Server /Listener socket that then is converted
into a Secure socket using OpenSSL library. This is compiled and built in a
Windows x64 environment. We also built the OpenSSL for the
returned by ERR_get_error and split by ERR_GET_LIB,
ERR_GET_FUNC, and ERR_GET_REASON into constants that I can use in a switch
statement to react to BIO errors. This is not a problem for SSL filter BIOs
since those have their own error reporting functions, but is a problem for
Internet socket
On Wed, Oct 28, 2020 at 04:32:56PM +0100, Jakob Bohm via openssl-users wrote:
> Recently, the EJBCA developers publicly warned (via the Mozilla root store
> policy mailing list) other CA vendors that they had incorrectly implemented
> the handling of the "notAfter" X509 field, resulting in
j 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded
Hi,
from nginx-dev list.
SSL: workaround for incorrect SSL_write() errors in OpenSSL 1.1.1.
OpenSSL 1.1.1 fails to return SSL_ERROR_SYSCALL if an error happens
during SSL_write() after close_notify alert from the peer, and returns
SSL_ERROR_ZERO_RETURN instead. Broken by this commit, which
On 13/05/2020 02:14, abel alejandro wrote:
> At the end I was able to get rid of the warnings and download without
> data corruption by using OPENSSL_ia32cap="~0x202". Could
> this be a bug somewhere in openssl or my hardware is just bad?
It could be a bug. I suggest you raise a
Hello all,
I have a AMD 3600x + X470D4U system where I observed intermittent ssl
problems including data corruption of files when downloading thru
https.
For example:
root@oasis:~# curl -o o https://www.google.com
% Total% Received % Xferd Average Speed TimeTime Time Current
ucontext.h existed in 2017 in Cygwin, and still exists.
Maybe you have a very old Cygwin (you can update with setup.exe).
Hello,
You could try with
./config no-async
Kind Regards,
Georg
Von: openssl-users Im Auftrag von Anand
Sridharan
Gesendet: 06 May 2020 03:20
An: openssl-users@openssl.org
Betreff: openssl-1.1.1g cygwin make errors
Hi Open SSL users ,
Please let us know if someone has observed below
Hi Open SSL users ,
Please let us know if someone has observed below errors while compiling on
source with cygwin.
Please do indicate any workaround available , I observed similar errors
with different version as well such as openssl 1.1.1a.
from crypto/async/arch/async_null.c:11:
crypto/async
enssl-1.1.1f'
make[1]: Entering directory `/home/birdnofoots/openssl-1.1.1f'
/usr/bin/perl apps/progs.pl <http://progs.pl/> apps/openssl > apps/progs.h
….
….
./test/recipes/90-test_sysdefault.t (Wstat: 512 Tests: 0 Failed: 0)
Non-zero exit status: 2
Parse errors: No plan
enssl-1.1.1f'
make[1]: Entering directory `/home/birdnofoots/openssl-1.1.1f'
/usr/bin/perl apps/progs.pl <http://progs.pl/> apps/openssl > apps/progs.h
….
….
./test/recipes/90-test_sysdefault.t (Wstat: 512 Tests: 0 Failed: 0)
Non-zero exit status: 2
Parse errors: No plan
> From: Venkata Ramaraju Vana [mailto:venkataramaraju.v...@broadcom.com]
> Sent: Thursday, February 06, 2020 03:01
> Error 209 error C2143: syntax error : missing ';' before '{'
>
> Error in "opensslconf.h" points to 'extern "C"' statement the following code:
> #ifdef __cplusplus
> extern "C" {
Thanks for the suggestion Michael. We have removed all duplicates of
"opensslconf.h" from our code stack. With those changes, we see all errors
related to "DEPRECATEDIN_1_1_0" are gone. Now, we are not seeing any errors
pointing to "bio.h". However, we have some
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> Venkata Ramaraju Vana via openssl-users
> Sent: Wednesday, February 05, 2020 00:40
> Error 300 error C3646: 'DEPRECATEDIN_1_1_0' : unknown override specifier
> xx\thirdparty\openssl\include\openssl\bio.h 689 1
Hi All,
We have recently upgraded openssl from 1.0.1h to 1.1.1d. We have
compiled OpenSSL using "no-asm no-shared no-deprecated" as input to
configure.
When compiling our application (in Visual Studio 2013) by including these
headers and libraries, we are seeing many er
I think it has nothing to do with OpenSSL.
On Fri, Nov 15, 2019 at 3:00 AM Krista Brackin via openssl-users <
openssl-users@openssl.org> wrote:
> I am a novice...so any help please
>
> Below is the stack trace on the outbound file but I cannot make any
> setting change workthoughts on
I am a novice...so any help please
Below is the stack trace on the outbound file but I cannot make any setting
change workthoughts on what could be blocked me from transferring the file?
log attached.
thank you!Krista
FTP was not successful com.tms.common.lib.FTPClient.FTPException:
Hi Matt,
Thanks for your help. I am able to proceed now.
Thanks and regards,
Nagalakshmi
-Original Message-
From: Matt Caswell
Sent: Wednesday, October 30, 2019 7:55 PM
To: Nagalakshmi V J ; openssl-users@openssl.org
Subject: Re: OpenSSL compilation errors in Windows
** This mail has
On 29/10/2019 11:55, Nagalakshmi V J wrote:
> Hi Matt,
>
> Thank you so much for your response. Those mentioned APIs resolved my
> errors.
>
> For the below code,
>
> return SSL_get_session(pConnection) != NULL &&
> pConnection->ses
Hi Matt,
Any inputs on the below query?
Thanks and regards,
Nagalakshmi
From: Nagalakshmi V J
Sent: Tuesday, October 29, 2019 5:25 PM
To: Matt Caswell ; Nagalakshmi V J
; openssl-users@openssl.org
Subject: Re: OpenSSL compilation errors in Windows
Hi Matt,
Thank you so much for your response
Hi Matt,
Thank you so much for your response. Those mentioned APIs resolved my errors.
For the below code,
return SSL_get_session(pConnection) != NULL &&
pConnection->session->session_id_length != 0;
Any reference for accessing session_id_length?
https://www.op
On 29/10/2019 10:34, Nagalakshmi V J wrote:
>
> tls1_PRF(s->ctx->md5,s->ctx->sha1,buf,(int)(p-buf),
>
> pGenerator->master_secret,sizeof(pGenerator->master_secret),
>
> km,tmp,num);
It seems your code is replicating parts of libssl - which seems like a
strange (and
nSSL compilation errors in Windows
Hi Matt,
Kindly provide your inputs for the below mail.
Thanks & Regards,
Nagalakshmi V J
From: Nagalakshmi V J
Sent: 22 October 2019 10:41:40
To: Matt Caswell ; openssl-users@openssl.org
Cc: Nagalakshmi V J
Subject: RE: OpenSSL com
Hi Matt,
Kindly provide your inputs for the below mail.
Thanks & Regards,
Nagalakshmi V J
From: Nagalakshmi V J
Sent: 22 October 2019 10:41:40
To: Matt Caswell ; openssl-users@openssl.org
Cc: Nagalakshmi V J
Subject: RE: OpenSSL compilation errors in Win
, void *p2);
} /* EVP_MD */ ;
Thanks and regards,
Nagalakshmi
From: Nagalakshmi V J
Sent: Tuesday, October 22, 2019 9:39 AM
To: Matt Caswell ; Nagalakshmi V J
; openssl-users@openssl.org
Subject: Re: OpenSSL compilation errors in Windows
Hi Matt,
Yes. Exactly we followed the same and able to resolve e
Hi Matt,
Yes. Exactly we followed the same and able to resolve errors. Thank you so much
for the support and guidance. I'll get back if any further errors.
Thanks & Regards,
Nagalakshmi V J
From: Matt Caswell
Sent: 21 October 2019 21:26:32
To: Nagalakshmi
hanks & Regards,
> Nagalakshmi V J
>
> *From:* Matt Caswell
> *Sent:* 18 October 2019 14:48:33
> *To:* Nagalakshmi V J ;
> openssl-users@openssl.org
> *Subject:* Re: OpenSSL compilation errors in Windo
: 18 October 2019 14:48:33
To: Nagalakshmi V J ; openssl-users@openssl.org
Subject: Re: OpenSSL compilation errors in Windows
** This mail has been sent from an external source **
On 18/10/2019 11:49, Nagalakshmi V J wrote:
> Now the issue is SSL_session structure is also having accessor APIs
&g
On 18/10/2019 11:49, Nagalakshmi V J wrote:
> Now the issue is SSL_session structure is also having accessor APIs
> which I am not aware of. So I need to get the APIs for accessing the
> master_key_length,etc.. given in the above code. Those are not listed
> in the openssl link referred.
On
Caswell
Sent: Thursday, October 3, 2019 6:51 PM
To: openssl-users@openssl.org
Subject: Re: OpenSSL compilation errors in Windows
** This mail has been sent from an external source **
On 03/10/2019 11:10, Nagalakshmi V J wrote:
> Hi Matthias,
>
>
>
> Please find my response for your queri
of accessor functions, I got the following APIs.
>
> SSL_get_session(s)
>
> SSL_SESSION_get_master_key().
>
>
>
> If we use those APIs, I am again getting errors like the below.
>
> /.\odlibPrf_OSSL.h(164) : error C2027: use of undefined type 'ssl_session_st'/
accessor
functions (a.k.a. getters and setters).
[Nagalakshmi]:
Regarding usage of accessor functions, I got the following APIs.
SSL_get_session(s)
SSL_SESSION_get_master_key().
If we use those APIs, I am again getting errors like the below.
.\odlibPrf_OSSL.h(164) : error C2027: use
@openssl.org; Umamaheswari Nagarajan
Subject: Re: OpenSSL compilation errors in Windows
** This mail has been sent from an external source **
Several people have told you the following:
That is an *internal* openssl header file; do not use it.
Remove the include statement from your
. Pierre
Sent: Tuesday, October 1, 2019 4:43 PM
To: Nagalakshmi V J
Cc: openssl-users@openssl.org; Umamaheswari Nagarajan
Subject: AW: OpenSSL compilation errors in Windows
** This mail has been sent from an external source **
> We are using OpenSSL APIs in our product code. We are not mak
Several people have told you the following:
That is an *internal* openssl header file; do not use it.
Remove the include statement from your code. Your code is wrong.
That file is a C file, not compatible with C++
Why do you not listen?
> We are using OpenSSL APIs in our product code. We are not making any changes
> in OpenSSL.
> Our product code is a C++ code and it makes use of openSSL APIs for some
> functionality.
Local headers (like "ssl_locl.h" and "packet_locl.h") are *NOT* part of the
official OpenSSL API.
Please
a '-fpermissive' flag which is suppressing those errors as
warnings and so compilation is getting successful.
The issue here is in Windows , we are not able to find alternative flag for
-'fpermissive' in Visual studio and due to that compilation is unsuccessful. It
would be helpful if anyone suggests some
; Umamaheswari
Nagarajan
Subject: AW: OpenSSL compilation errors in Windows
> OpenSSL code is compiling without any issues. When it is used from our
> product code and while compiling using C++ compiler, the issue is seen.
As I wrote previously, the error you posted was caused by th
> OpenSSL code is compiling without any issues. When it is used from our
> product code and while compiling using C++ compiler, the issue is seen.
As I wrote previously, the error you posted was caused by the fact that you
are compiling Ansi C (a.k.a ISO/IEC 9899:1990, a.k.a C90) source code
Hi Michael,
OpenSSL code is compiling without any issues. When it is used from our product
code and while compiling using C++ compiler, the issue is seen.
We also don’t use the ‘warning as errors’ and warning level 3 we are using
currently.
Thanks and regards,
Nagalakshmi
From: Michael
rs@openssl.org
> Cc: Umamaheswari Nagarajan
> Subject: AW: OpenSSL compilation errors in Windows
>
>
>
> ** This mail has been sent from an external source **
>
>
>
>
>
>> Getting the errors like below. ssl/packet_locl.h(429) : error C2440:
>
>>
To: Nagalakshmi V J ; openssl-users@openssl.org
Cc: Umamaheswari Nagarajan
Subject: AW: OpenSSL compilation errors in Windows
** This mail has been sent from an external source **
> Getting the errors like below. ssl/packet_locl.h(429) : error C2440:
> '=' : cannot convert from 'void *' to 'un
We compile using Visual Studio. We don't use 'warnings as errors' and
selected a warning level that minimized warnings. The 'make test' runs
cleanly.
On Mon, Sep 30, 2019, 3:16 AM Nagalakshmi V J
wrote:
> Hi,
>
> I am using openssl 1.1.c from our product code. While compiling the cod
> Getting the errors like below. ssl/packet_locl.h(429) : error C2440: '=' :
> cannot convert from 'void *' to 'unsigned char 'Conversion from 'void' to
> pointer to non-'void' requires an explicit cast
Is it possible that your error message was copied incorrectly? Line 429 is an
a
Hi,
I am using openssl 1.1.c from our product code. While compiling the code, I am
getting the errors which can be suppressed as warnings using -fpermissive flag
in Linux (gcc/g++). In windows, I am getting the same compilation errors in
visual studio (2005). Would like to know the alternative
Did you read my previous response, where I listed the relevant Configure
options? Be sure to expand included text, if you're using one of those
braindead MUAs which hide it.
Are there additional commands I have to pass to the Configure module if I want
to build completely static libs? If so, what are they?
Again, please don't send questions about OpenSSL directly to me. I am not a
member of the OpenSSL Project.
> From: Osman Zakir [mailto:osmanzaki...@hotmail.com]
> Sent: Saturday, September 14, 2019 10:54
> I'm not trying to build a DLL, though. I want to build a static .lib library
> (are
> From: Osman Zakir [mailto:osmanzaki...@hotmail.com]
> Sent: Friday, September 13, 2019 18:06
> I won't build with either one enabled if that's better, but I'd still like to
> know how
> to fix those linker errors.
Someone should probably look into that, but I don't have time to
I'll just put both email addresses in for "To" then.
I won't build with either one enabled if that's better, but I'd still like to
know how to fix those linker errors.
I do also want to ask what AFALG is and if I should enable it or not (and what
happens if I do).
> From: Osman Zakir [mailto:osmanzaki...@hotmail.com]
> Sent: Friday, September 13, 2019 13:26
> I had a successful build before I configured it again to try to get MD2 and
> RC5, so I
> didn't see a reason to clean the build.
Reconfiguring changes the makefiles. You should always clean after a
I had a successful build before I configured it again to try to get MD2 and
RC5, so I didn't see a reason to clean the build. I did clean it now after the
failure happened.
I'll try to fix these errors for now, so please help me with that. But I also
want to know after that whether
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> Osman Zakir
> Sent: Friday, September 13, 2019 11:30
> I had linker errors when trying to build OpenSSL with MD2 and RC5 support.
Did you clean after configuring?
> I'm also tempted to try get
I had linker errors when trying to build OpenSSL with MD2 and RC5 support. I
ran this command:
"
perl Configure VC-WIN64A --with-zlib-lib=C:/zlib/lib/zlibstatic
--with-zlib-include=C:/zlib/include enable-md2 enable-rc5 --release
"
and had the messages I've put in this Gist in
> On Jul 18, 2019, at 3:13 PM, Mark Richter wrote:
>
> 2. Not at all clear on what the "_OPT" part means - do I need to change my
> source code to use this for accessors or ???
Just try it and see. The "_OPT" in the symbol version is internally
generated from "-opt" in the shlib_variant
> On Jul 18, 2019, at 2:57 PM, Mark Richter wrote:
>
> Also, once I figure out the build issues, how can I statically link the ssl
> libraries into my app? (That way we don't require our customers to build and
> install OpenSSL 1.1.1 pon their RHEL 7 hosts.) Are there any gotchas to
> doing
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> Mark Richter
> Sent: Thursday, July 18, 2019 12:57
>
> Is Linux considered to be the same as (or similar enough to) Unix w.r.t. the
> building instructions? I'm reading the INSTALL file and it doesn't mention
> Linux
> -Original Message-
> From: openssl-users On Behalf Of Viktor
> Dukhovni
> Sent: Wednesday, July 17, 2019 12:42 PM
> To: openssl-users@openssl.org
> Subject: Re: Errors building 1.1.1 on RHEL 7
>:
> 4. Build and install OpenSSL 1.1.1c with "--prefix=/opt/o
-Original Message- [edited]
From: openssl-users On Behalf Of Viktor
Dukhovni
Sent: Wednesday, July 17, 2019 6:17 PM
To: openssl-users@openssl.org
Subject: Re: Errors building 1.1.1 on RHEL 7
>>> 2. Configure your OpenSSL build to use the corresponding "rpath":
>&
Probably, disregard: the problem seems to be related to the incomplete support
for ISO C11 in GCC on CentOS (and I'm willing to bet - on RHEL).
Changing the standard to "-std=gnu99" lead to a successful build with all the
tests passing.
On 7/18/19, 12:28 PM, "openssl-users on behalf of
I'm getting a somewhat different error trying to build OpenSSL_1_1_1-stable on
CentOS 7 (similar to RHEL 7).
Configuration:
./config --prefix=$HOME/openssl-1.1 --debug --openssldir=$HOME/openssl-1.1/etc
--with-rand-seed=rdcpu enable-aria enable-ec_nistp_64_gcc_128 enable-md2
enable-rc5
On Thu, Jul 18, 2019 at 12:54:51AM +, Mark Richter wrote:
> I'm still really new at this - a few questions:
Understood.
> 1. Choose some location that is not on the default library search path
> to install the 1.1.1 custom libraries. I use /opt/openssl/1.1/lib
>
> > How do I specify
I'm still really new at this - a few questions:
-Original Message-
From: openssl-users On Behalf Of Viktor
Dukhovni
Sent: Wednesday, July 17, 2019 12:42 PM
To: openssl-users@openssl.org
Subject: Re: Errors building 1.1.1 on RHEL 7
On a system with OpenSSL 1.0.2 or OpenSSL 1.1.0 in /usr
> On Jul 17, 2019, at 3:41 PM, Viktor Dukhovni
> wrote:
>
> On a system with OpenSSL 1.0.2 or OpenSSL 1.1.0 in /usr/lib (on the default
> search path), and especially when you're linking with other libraries that
> in turn were linked against the OpenSSL version in /usr/lib, using OpenSSL
>
On a system with OpenSSL 1.0.2 or OpenSSL 1.1.0 in /usr/lib (on the default
search path), and especially when you're linking with other libraries that
in turn were linked against the OpenSSL version in /usr/lib, using OpenSSL
1.1.1 in your application requires care...
> On Jul 17, 2019, at 2:22
It works better with 1.1.1c.
Thank you.
-Original Message-
From: Matt Caswell
Sent: Wednesday, July 17, 2019 1:16 AM
To: Mark Richter ; openssl-users@openssl.org
Subject: Re: Errors building 1.1.1 on RHEL 7
On 16/07/2019 23:27, Mark Richter wrote:
> Result: PASS
Well that's qu
bcrypto.so.10, needed by /usr/lib64/libssh2.so.1, may
conflict with libcrypto.so.1.1
I tried googling this and get lots of suggestion for similar errors with
libcurl, but not this one.
What am I missing?
-Original Message-
From: Jan Just Keijser
Sent: Wednesday, July 17, 2019 2:53 A
n perl" or "perldoc perl". If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.
Mark Richter | Senior Staff Engineer
SolarFlare Communications, Inc. | www.Solarflare.com
9444 Waples Street, #170, San Diego, CA 92121
Mobile: +1 949-
Inc. | www.Solarflare.com
> 9444 Waples Street, #170, San Diego, CA 92121
> Mobile: +1 949-632-8403
>
>
>
> From: openssl-users on behalf of Matt
> Caswell
> Sent: Tuesday, July 16, 2019 3:20 PM
> To: openssl-users@openssl.org
> Subject: Re: Errors building 1.1
Staff Engineer
SolarFlare Communications, Inc. | www.Solarflare.com
9444 Waples Street, #170, San Diego, CA 92121
Mobile: +1 949-632-8403
From: openssl-users on behalf of Matt
Caswell
Sent: Tuesday, July 16, 2019 3:20 PM
To: openssl-users@openssl.o
On 16/07/2019 22:23, Mark Richter wrote:
> After I built version 1.1.1 on RHEL 7, I got these errors at the end of the
> 'make test.' What do they mean?
>
>
> Test Summary Report
> ---
> ../test/recipes/15-test_dsa.t(Wstat: 768
On Tue, Jul 16, 2019 at 09:23:32PM +, Mark Richter wrote:
> After I built version 1.1.1 on RHEL 7, I got these errors at the end of the
> 'make test.' What do they mean?
The test scripts exited with non-zero exit codes.
> Test Summary Report
> ---
> ../
After I built version 1.1.1 on RHEL 7, I got these errors at the end of the
'make test.' What do they mean?
Test Summary Report
---
../test/recipes/15-test_dsa.t(Wstat: 768 Tests: 6 Failed: 3)
Failed tests: 4-6
Non-zero exit status: 3
../test/recipes/15
Anyone getting this in the last 2 days?
../test/recipes/30-test_evp.t .. Dubious, test returned 1
(wstat 256, 0x100)
Failed 1/10 subtests
--
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President
On 19/06/2019 19:07, Samiya Khanum via openssl-users wrote:
> Hi,
>
> While compiling async I see below errors with UCLIBC.
>
> /libcrypto.so: undefined reference to `getcontext'
> libcrypto.so: undefined reference to `setcontext'
> libcrypto.so: undefined refe
Hi,
While compiling async I see below errors with UCLIBC.
*libcrypto.so: undefined reference to `getcontext'libcrypto.so: undefined
reference to `setcontext'libcrypto.so: undefined reference to `makecontext'*
As UCLIBC doesn't have support to these APIs, i have added no-async in
configure
On 01/03/2019 12.34, Sravani Maddukuri via openssl-users wrote:
> Hi,
>
> Earlier our application used OpenSSL version 1.0.2n. Now we wanted to
> upgrade to 1.1.1b.
> After upgrade when i compile OpenSSL, i see the following errors:
>
> Tried to generate the Makefile with bo
Hi,
Earlier our application used OpenSSL version 1.0.2n. Now we wanted to
upgrade to 1.1.1b.
After upgrade when i compile OpenSSL, i see the following errors:
Tried to generate the Makefile with both the ways mentioned below..
But getting compilation errors as attached mainly at places
where
On 1/18/19 1:05 AM, Dennis Clarke wrote:
So it seems to no longer matter if I try strict C99 or just cc with or
without strict CFLAGS. I always arrive at the same place :
Ignore this .. fixed .. done .. closed ... not even a correct issue.
Thou shalt not pass C99 here. Thus sayeth the Salz
/rsa_complex.o
OPENSSL_sk_deep_copytest/rsa_complex.o
OPENSSL_sk_find_ex test/rsa_complex.o
ld: fatal: symbol referencing errors. No output written to test/rsa_complex
gmake[1]: *** [Makefile:3561: test/rsa_complex] Error 2
gmake[1]: Leaving directory
'/usr/local/build
The "which package depends on which openssl ver" issue's been around a long
time.
FWIW, in general, I *never* touch openssl libs/headers in the default
distro path, /usr.
Just leave that alone -- too many distro packages (still) make (invalid)
assumptions about that being the only/preferred
If the compiler found opensslconf.h in
/usr/include/x86_64-linux-gnu/openssl/, that usually means you have an
distribution openssl package installed, one that other programs are
relying on.
Depending on the version of that package, you may have screwed things
up or not. If you're lucky, things
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
1 - 100 of 516 matches
Mail list logo
