I found it , let me try compiling it. (./config was reporting error)
thanks
>> perl Configure LIST|grep linux-x86_64
linux-x86_64
linux-x86_64-clang
I see, below command seems to be working -
>> ./Configure --prefix=/opt/openssl-1.1.1o --openssldir=/opt/openssl/1.1.1o
>> --s
On 23/06/2022 12:31, Gaurav Mittal11 wrote:
I am running redhat 5.11 Linux, probably this command is not supported.
Although I have manually compiled latest perl version
-bash-3.2$ perl -v
This is perl 5, version 36, subversion 0 (v5.36.0) built for x86_64-linux
-bash-3.2$ perl Configure
I am running redhat 5.11 Linux, probably this command is not supported.
Although I have manually compiled latest perl version
-bash-3.2$ perl -v
This is perl 5, version 36, subversion 0 (v5.36.0) built for x86_64-linux
-bash-3.2$ perl Configure LIST
Can't open perl script "Configure
On 22/06/2022 15:32, Gaurav Mittal11 wrote:
This system (linux-x86_64) is not supported. See file INSTALL for details.
That is very odd. I would expect linux-x86_64 to always be reported as
supported by config.
Do you get sensible output from:
$ perl Configure LIST
You should see a
It is not building at all, This system (linux-x86_64) is not supported.
Regards,
Gaurav Mittal
-Original Message-
From: openssl-users On Behalf Of Ken Goldman
Sent: 22 June 2022 09:44 PM
To: openssl-users@openssl.org
Subject: [EXTERNAL] Re: Openssl upgrade to 1.1.1o on Red Linux 5.11
On 6/22/2022 10:32 AM, Gaurav Mittal11 wrote:
Hi Team,
Is there any way to upgrade openssl in redhat 5.11 as I am getting error its
not supported.
> uname -a
Linux serverxxx 2.6.18-419.el5 #1 SMP Wed Feb 22 22:40:57 EST 2017 x86_64
x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Ser
Hi Team,
Is there any way to upgrade openssl in redhat 5.11 as I am getting error its
not supported.
> uname -a
Linux serverxxx 2.6.18-419.el5 #1 SMP Wed Feb 22 22:40:57 EST 2017 x86_64
x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 5.11 (Tikanga)
>> ./config --pr
On Fri, Jun 10, 2022 at 09:43:45AM -0400, Dennis Clarke via openssl-users wrote:
> I am surprised that people are not hitting this wall on all
> platforms. Pushing out a new release jsut for an expired test
> certificate seems a tad silly but perhaps ALL the test certs can
> be updated at the same
ennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
On 09/06/2022 21:13, Dennis Clarke via openssl-users wrote:
On 6/9/22 15:33, Dmitry Belyavsky wrote:
It happens because of certificates expiration. Try applying the patch
from
https://github.com/openssl/openssl/pull/18444
Oh cool. Thank you. Sadly I do not see a patch file there.
You c
allclock secs ( 0.06 usr 0.01 sys + 1.36 cusr
0.05 csys = 1.48 CPU)
Result: NOTESTS
Files=0, Tests=0, 0 wallclock secs ( 0.00 usr + 0.00 sys = 0.00 CPU)
Result: NOTESTS
make[1]: Leaving directory `/opt/bw/build/openssl-3.0.3_rhel6_amd64.005'
mimas$
So maybe this is a nothing. Hard to s
/MA0GCSqGSIb3DQEBCwUAA4GBAD0aYh9OkFYfXV7kBfhrtD0PJG2U47OV/1qq
+uFpqB0S1WO06eJT0pzYf1ebUcxjBkajbJZm/FHT85VthZ1lFHsky87aFD8XlJCo
2IOhKOkvvWKPUdFLoO/ZVXqEVKkcsS1eXK1glFvb07eJZya3JVG0KdMhV2YoDg6c
Doud4XrO
-END CERTIFICATE-
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and
tory `/opt/bw/build/openssl-3.0.3_rhel6_amd64.005'
> make: *** [tests] Error 2
>
>
>
>
> --
> Dennis Clarke
> RISC-V/SPARC/PPC/ARM/CISC
> UNIX and Linux spoken
> GreyBeard and suspenders optional
>
--
SY, Dmitry Belyavsky
SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
compile. Thus far anyways.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
ds the new OpenSSL 3 wants. Could be C90 per the old OpenSSL 1.x
or maybe we need C99. Regardless the whole show stops fast on RHEL6 and
yes I do have gcc 12.1.0 bootstrapped and tested as well as new binutils
and a pile of other newish stuff. I have tried :
/opt/bw/bin/perl ./Configure linux-x86
=/usr/lib/ssl-3 --libdir=/usr/lib linux-armv4
The output of openssl version -a is as follows.
OpenSSL 3.0.0 7 sep 2021 (Library: OpenSSL 3.0.0 7 sep 2021)
built on: Tue Sep 7 11:46:32 2021 UTC
platform: linux-armv4
options: bn(64,32)
compiler: arm-poky-linux-gnueabi-gcc -mthumb -mfpu=neon -mfloat
Hi Susan,
How did you run Configure? Are you cross compiling?
Be default, OpenSSL 3.0.0 builds for /usr/local. Your MUST install it there or
use a Configure option if you want to install it somewhere else.
Kory
> On Nov 9, 2021, at 2:21 PM, Susan Tremel wrote:
>
> I’ve successfully built an
I've successfully built and installed openssl 3.0 and the fips.so module in
my yocto build environment. My goal is to make the FIPs module the default
provider for all applications so I modified my openssl.cnf file to match
the docs like the following.
config_diagnostics = 1
openssl_c
tend to stay on LTS
solutions.I do patch weekly.
From: Jan Just Keijser
Sent: Monday, May 31, 2021 8:45 AM
To: Michael McKenney ; openssl-users@openssl.org
Subject: Re: Why can't we get a proper installation method to keep OpenSSL at
the latest revision for Linux?
Hi,
On 31/05/21
31, 2021 5:55 AM
*To:* Michael McKenney ;
openssl-users@openssl.org
*Subject:* Re: Why can't we get a proper installation method to keep
OpenSSL at the latest revision for Linux?
On 30/05/21 14:05, Michael McKenney wrote:
Why can't we get a proper installation method to keep
atest revision for Linux?
On Mon, May 31, 2021 at 7:02 AM Michael McKenney via openssl-users
wrote:
>
> My wordpress servers are under constant attack. My Fortinet 60E firewall
> logs are filled. Openssl is constantly reported on The Hacker News and other
> sites. So I don’t ne
Keijser
; openssl-users@openssl.org
Subject: Re: Why can't we get a proper installation method to keep OpenSSL at
the latest revision for Linux?
If you use a supported distro (i.e., one that is not out of life) then the
distro is expected to supply CVE issue fixes in form of updates.
They us
7;t we get a proper installation method to keep OpenSSL at
> the latest revision for Linux?
>
>
>
> On 30/05/21 14:05, Michael McKenney wrote:
>
> Why can't we get a proper installation method to keep OpenSSL at the latest
> revision for Linux?
>
> My biggest co
May 31, 2021 5:55 AM
> To: Michael McKenney ;
> openssl-users@openssl.org
> Subject: Re: Why can't we get a proper installation method to keep
> OpenSSL at the latest revision for Linux?
>
> On 30/05/21 14:05, Michael McKenney wrote:
> > Why can't we get a proper ins
method to keep OpenSSL at
the latest revision for Linux?
On 30/05/21 14:05, Michael McKenney wrote:
Why can't we get a proper installation method to keep OpenSSL at the latest
revision for Linux?
My biggest compliant with Linux is it is so difficult to get best practice
installations fo
On 30/05/21 14:05, Michael McKenney wrote:
Why can't we get a proper installation method to keep OpenSSL at the
latest revision for Linux?
My biggest compliant with Linux is it is so difficult to get best
practice installations for services like OpenSSL. Ubuntu is still on
1.1.1f.
s, Ubuntu has a package changelog.
Cheers, Marian
Am So., 30. Mai 2021 um 14:06 Uhr schrieb Michael McKenney <
mike.mcken...@scsiraidguru.com>:
> Why can't we get a proper installation method to keep OpenSSL at the
> latest revision for Linux?
>
> My biggest compliant with L
Why can't we get a proper installation method to keep OpenSSL at the latest
revision for Linux?
My biggest compliant with Linux is it is so difficult to get best practice
installations for services like OpenSSL. Ubuntu is still on 1.1.1f.I have
been trying to upgrade to 1.1.1k. Op
On 05/04/21 17:16, Boris Shpoungin via openssl-users wrote:
Hello,
Is there minimal requirements for Linux kernel for usage of openssl
library version 1.1.1?
I have old application based on Linux kernel 3.0.8 which uses openssl
version 1.0.2. My question is whether it is possible to port
n using openssl 1.1.1 and see
if/where it breaks.
If you are worried about the combination of Linux 3.0.8 plus the switch
from openssl 1.0.2 -> 1.1.1 then I'd suggest a three step process
1) build openssl 1.1.1 on your old kernel and run 'make test' if that
passes, then opens
er it describes ALL required modification?
On Monday, April 5, 2021, 03:57:36 PM EDT, Viktor Dukhovni
wrote:
> On Apr 5, 2021, at 11:16 AM, Boris Shpoungin via openssl-users
> wrote:
>
> Is there minimal requirements for Linux kernel for usage of openssl library
> versio
> On Apr 5, 2021, at 11:16 AM, Boris Shpoungin via openssl-users
> wrote:
>
> Is there minimal requirements for Linux kernel for usage of openssl library
> version 1.1.1?
>
> I have old application based on Linux kernel 3.0.8 which uses openssl version
> 1.0.2. My q
Hello,
Is there minimal requirements for Linux kernel for usage of openssl library
version 1.1.1?
I have old application based on Linux kernel 3.0.8 which uses openssl version
1.0.2. My question is whether it is possible to port this application to use
openssl version 1.1.1 in Linux 3.0.8
I'm still struggling with this problem, but I have a little more
information. I learned from a close reading of `INSTALL.W32` and `.W64`
that support for 64-bit Windows is not stable, but support for 32-bit
Windows is okay, and that cross-compilation from Linux is possible. An
example giv
Hi there:
I'm trying to cross-compile FIPS-capable OpenSSL from Linux to Windows.
I already have a working native Linux build system, and I want to
extend it to support Windows targets without standing up a new host.
My cross-compile process follows the FOM User Guide to the best
Guide on Renewing SSL Certificate for Apache, Postfix and Dovecot on CentOS
6.8 Linux
=
Author: Mr. Turritopsis Dohrnii Teo En Ming (TARGETED INDIVIDUAL)
Country: Singapore
Date: 12 November 2020 Thursday
This is the mailinglist of OpenSSL not OpenSSH.
Hi,
The ask is the server IP during ssh user@server ip.when it reaches the
server's Pam, is there a way to get the local address in Pam context.
Please support
Thanks and regards,
Apphia
Subject: How to Migrate Wordpress Website from 32-bit CentOS Linux 6.3 to
64-bit CentOS Linux 8.2 (2004)
Author of this Guide: Mr. Turritopsis Dohrnii Teo En Ming (TARGETED INDIVIDUAL)
Country: Singapore
Date: 31 August 2020 Monday Singapore Time
Type of Publication: Plain Text
Document
the same one as reported by John
Baldwin in the thread "Testing TLS 1.0 with OpenSSL master").
Matt
>
>
> On 05/08/2020 22:19, Skip Carter wrote:
>> Patrick,
>>
>> I am also supporting servers running very old Linux systems and I can
>> tell you that
Hi guy,
Can somebody give me a hint for the following topic please?
I want to cross compile the latest openssl v1.1 on linux (centos 7) as target
macos 32/64 bit.
Thanks in advance
Tobi
nt by some not-that-old web browsers.
On 05/08/2020 22:19, Skip Carter wrote:
Patrick,
I am also supporting servers running very old Linux systems and I can
tell you that YES you can upgrade from source. I have built
openssl-1.1.1 from source on such systems with no problems.
On Wed, 2020-0
On Thu, Aug 06, 2020 at 09:24:32PM +0200, Patrick Mooc wrote:
> Thank you Ben for your answer.
>
> I had a look today for this point, but I didin't found anything about
> extension in the OpenSSL version I use (0.9.8).
If I am mistaken, OpenSSL 0.9.8 shuld have support for the SNI
extension. It
solve my problem without
upgrading OpenSSL version or Linux distribution, It would be very
nice.
Thank you in advance for your answer.
Best Regards,
Le 05/08/2020 à 22:10, Kyle Hamilton a écrit :
It is never recommended to upgrade you distribution's version of
Open
Hello Hubert,
Thank you for your answser.
I already did this test, but also without success.
Best Regards,
Le 07/08/2020 à 18:18, Hubert Kario a écrit :
On Thursday, 6 August 2020 21:24:32 CEST, Patrick Mooc wrote:
Thank you Ben for your answer.
I had a look today for this point, but I did
> SSLv2 protocol.
>
>
> Thus, if you have any idea of how to solve my problem without upgrading
> OpenSSL version or Linux distribution, It would be very nice.
>
>
> Thank you in advance for your answer.
>
> Best Regards,
>
>
> Le 05/08/2020 à 22:10, Kyle H
On Thursday, 6 August 2020 21:24:32 CEST, Patrick Mooc wrote:
Thank you Ben for your answer.
I had a look today for this point, but I didin't found anything
about extension in the OpenSSL version I use (0.9.8).
Maybe I have to modify OpenSSL configuration file
(openssl.conf) and compile Open
hus, if you have any idea of how to solve my problem without upgrading
OpenSSL version or Linux distribution, It would be very nice.
Using an "SSLv2-compatible" ClientHello is rather distinct from actually using
the SSLv2 protocol; I believe that the former is what is happening for you.
use of
> SSLv2 protocol.
>
>
> Thus, if you have any idea of how to solve my problem without upgrading
> OpenSSL version or Linux distribution, It would be very nice.
Using an "SSLv2-compatible" ClientHello is rather distinct from actually using
the SSLv2 protocol; I belie
(in order to limit risks
as much as possible) ?
Thank you in advance.
Best Regards,
Le 05/08/2020 à 22:19, Skip Carter a écrit :
Patrick,
I am also supporting servers running very old Linux systems and I can
tell you that YES you can upgrade from source. I have built
openssl-1.1.1 from
LSv10 ciphers in OpenSSL
configuration and in application software, but I didn't succeed doing so.
That's why I had in idea of upgrading OpenSSL version to avoid the use
of SSLv2 protocol.
Thus, if you have any idea of how to solve my problem without upgrading
OpenSSL version or Linux d
Patrick,
I am also supporting servers running very old Linux systems and I can
tell you that YES you can upgrade from source. I have built
openssl-1.1.1 from source on such systems with no problems.
On Wed, 2020-08-05 at 21:49 +0200, Patrick Mooc wrote:
> Hello,
>
> I'm using
t; Hello,
>
> I'm using an old version of OpenSSL (0.9.8g) on an old Linux Debian
> distribution (Lenny).
>
> Is it possible to upgrade OpenSSL version without upgrading Linux Debian
> distribution ?
> If yes, up to which version of OpenSSL ?
>
> Are all versions of
Hello,
I'm using an old version of OpenSSL (0.9.8g) on an old Linux Debian
distribution (Lenny).
Is it possible to upgrade OpenSSL version without upgrading Linux Debian
distribution ?
If yes, up to which version of OpenSSL ?
Are all versions of OpenSSL compliant with all Linux D
I need two fuctions: sha512_block_data_order and sha256_block_data_order.
how can I get it.
Thank you
Hi,
I am using following openssl versions
openssl-1.0.2r.tar.gz
openssl-fips-2.0.5.tar.gz
Following are my files,
*foo.c* :
[root@data-domain-dev-vm poc]# cat foo.c
#include
#include
#include
int foo_func()
{
int rc, mode;
mode = FIPS_mode();
if(mode == 0)
{
rc = FIPS_
-
From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
Michael Wojcik
Sent: Monday, November 18, 2019 5:29 AM
To: openssl-users@openssl.org
Subject: RE: Static linking libssl.a and libcrypto.a on Linux x64 fails
> From: Aijaz Baig [mailto:aijazba...@gmail.com]
>
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> Kristen Webb
> Sent: Saturday, November 16, 2019 10:22
> It sounds like peeking at the port may be the simplest way to determine how
> it is
> being connected to.
Using different ports for different types of service
> From: Aijaz Baig [mailto:aijazba...@gmail.com]
> Sent: Wednesday, November 13, 2019 19:58
> However my current concern here is meeting libSSL and libCrypto's
> dependencies on
> host libraries on Linux platform. For instance, when I talked about 'linking'
>
be a linux server, so setting up peek should work well.
Apple has a network framework (supports TLS 1.3) that I believe will
eventually replace the current security framework (supports
up to TLS 1.2) that I am using today to get the job done. There is example
code here:
https://developer.appl
On Fri, Nov 15, 2019 at 03:10:55PM -0700, Kristen Webb wrote:
> Is there a way for a single program to act as both a TLS client and a TLS
> server after a TCP/IP accept() call?
Yes, but as you're aware and others have mentioned it has to decide
which somehow.
> Today, I simply have the TCP conne
enssl (with that extra TCP packet clue in place). I
> am more familiar
> with openssl and I'm trying to code everything there first. Also my
> entire application
> runs on linux so I am able to test all the combinations easily from
> there. And I'll
> need it to work w
can be done with Apple's network framework
> (at least not yet). It appears to be so high level as to not allow me
> to process a TCP packet within a TLS style connection.
It's not entirely clear to me what you're trying to do. Is this a fair
description?
1. You have a process (
I'm curious, its pretty unusual to not know which side of a TCP connection
is the client or server, not just TLS, HTTP, SMTP, etc. Its almost
always the side that makes the accept() call that's the server, but that
doesn't have to be.
Why is it that you do not in this context?
Without it, yo
ng to code everything there first. Also my entire
application
runs on linux so I am able to test all the combinations easily from there.
And I'll
need it to work with Apple's networking in the future as their security
APIs go away.
Thank you for bearing with me so far!
On Fri, Nov 15,
Yes, so you accept thread needs to either fork() or spawn another thread to
process the packet and go back into the accept loop for another connection.
-
Phillip Neumiller
Platform Engineering
Directstream, LLC
--
Sent from: http://openssl.6102.n7.nabble.com/OpenSSL-User-f3.html
Hi Phil,
Thanks for such a fast response! I am doing the polling today.
I believe I left something very important out of my original question.
I only have 1 well known port to accept all of my connections.
TLS_client_app -> service on portA (needs to be a TLS_server)
TLS_server_app -> service on
Sure, you just need additional threads. Note: accept is a blocking call so
the thread that runs in (i.e. your server side will block until a packet is
received). You can write a polling loop using select, that doesn't block.
The cleanest thing to do is have a thread for client(s) and one for ser
Is there a way for a single program to act as both a TLS client and a TLS
server after a TCP/IP accept() call?
Today, I simply have the TCP connecting process issue a 1 or 0 to indicate
how it is acting. This is then used to determine who does SSL_accept and
SSL_connect and everything works out.
ript command "ADDLIB" inside the provided
> MRI-style linker script.
> For more details see the "ar scripts" part of the full GNU BinUtils TexInfo
> manual.
> Enjoy
> Jakob
Well, I'll take a look however Mike's method is pretty easy enough to
fol
Thank you for the suggestion. Will try that.
Regarding the static library, the term 'linking' I used was more tongue in
cheek but nonetheless. However my current concern here is meeting libSSL
and libCrypto's dependencies on host libraries on Linux platform. For
instance, when
application (Linux).
You can't link anything into a Linux static library, technically.
ELF static libraries, like the older UNIX static libraries they're descended
from, are just collections of object files, possibly with some additional
metadata. (In BSD 4.x, for example, libraries often ha
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> Aijaz Baig
> Sent: Wednesday, November 13, 2019 01:45
> I am trying to statically link libssl.a and libcrypto.a into a static library
> of my own
> which I will be using in an application (Linux
(Linux). So I
first create that library (let's call it libAPP.a) and then I use that
library in an application. So first things first:
1. when I checkout the contents of that library (nm libAPP.a | less) ,
almost all (I haven't confirmed every single one but it sure looks that
way) S
I have downloaded and ran the following configuration for OpenSSL 1.1.1.d
./config shared --prefix=/opt/test/openssl -openssldir=/opt/test/openssl
Does anyone have any idea why I receive the following error when executing
"Make"
c1: error: apps/app_rand.d: No such file or directory
make[1]: ***
On Tue, 08 Oct 2019 18:53:37 +0200,
Dan Heinz wrote:
>
> Another question is why I now need to link pthreads when I did not
> in the 1.0.2 version? I've added no-threads to the configuration,
> but I'm curious why I didn't need to previously link it. And I'd
> prefer not to change too many confi
tps://github.com/openssl/openssl/issues/9036
> > >
> > > I thought I would try it out.
> > > I used your example and created my own config target in file named
> > > no_dos.conf.
> > > (
> > > 'my-linux-x86_64' => {
> > > inheri
workaround in this thread:
> > https://github.com/openssl/openssl/issues/9036
> >
> > I thought I would try it out.
> > I used your example and created my own config target in file named
> > no_dos.conf.
> > (
> > 'my-linux-x86_64'
054
>
> >Cheers,
> >Richard
>
> Thanks for the info. I did some more digging and you had actually posted a
> workaround in this thread:
> https://github.com/openssl/openssl/issues/9036
>
> I thought I would try it out.
> I used your example a
ted a
workaround in this thread:
https://github.com/openssl/openssl/issues/9036
I thought I would try it out.
I used your example and created my own config target in file named no_dos.conf.
(
'my-linux-x86_64' => {
inherit_from=> [ 'linux-x86_64' ],
developer, and not too adept with
> Linux.
>
> Our library has been using the OpenSSL 1.0.2x branch, and we are moving to
> 1.1.1c. I have the
> Windows build of our libraries working, and now I’ve moved to Linux.
>
> Our library is built as a shared library as well as
Please bear with me as I am a Windows developer, and not too adept with Linux.
Our library has been using the OpenSSL 1.0.2x branch, and we are moving to
1.1.1c. I have the Windows build of our libraries working, and now I've moved
to Linux.
Our library is built as a shared library as we
On 18/09/2019 20:58, Salz, Rich via openssl-users wrote:
Please take a look at
https://lore.kernel.org/lkml/CAHk-=wiGg-G8JFJ=r7qf0b+utqa_weouk6v+mcmfsljlrq6...@mail.gmail.com/
and consider giving your comments.
TL;DR: see the comment below.
+ * Hacky workaround for the fact that some proce
Please take a look at
https://lore.kernel.org/lkml/CAHk-=wiGg-G8JFJ=r7qf0b+utqa_weouk6v+mcmfsljlrq6...@mail.gmail.com/
and consider giving your comments.
TL;DR: see the comment below.
+ * Hacky workaround for the fact that some processes
+ * ask for truly secure random numbers and absolutely wa
On 25/03/2019 22:53, sebastien wrote:
hi
in a terminal I've got this error with
|openssl version openssl: /usr/lib/x86_64-linux-gnu/libssl.so.1.1:
version `OPENSSL_1_1_1' not found (required by openssl) openssl:
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: version `OPENSSL_1_1_1&#
hi
in a terminal I've got this error with
|openssl version openssl: /usr/lib/x86_64-linux-gnu/libssl.so.1.1:
version `OPENSSL_1_1_1' not found (required by openssl) openssl:
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: version `OPENSSL_1_1_1' not
found (required by openssl)
Hi
Not sure if any of the build / test process of OpenSSL utilise inbuilt KORN
Arithmetic & Test functions.
https://community.ubuntu.com/t/inbuilt-korn-arithmetic-test-functions-broken-under-windows-subsystem-for-linux/10089
<https://community.ubuntu.com/t/inbuilt-korn-arithmet
On Friday, 22 February 2019 11:28:33 CET Juan Isoza wrote:
> Hello,
> I want create for one of my application a Linux binary which run on all
> current linux system running x86_64 processor.
>
> by example, I uses -static-libgcc -static-libstdc++ when I link my app ,
> because
Hello Juan,
unfortunately is it not possible to static link the glibc.
You can try static link another libc like musl-libc [1].
Should there be any problems compiling OpenSSL with musl-libc, take a
look at the packages from Alpine Linux [2], they are using musl as their
standard libc.
You
Hello,
I want create for one of my application a Linux binary which run on all
current linux system running x86_64 processor.
by example, I uses -static-libgcc -static-libstdc++ when I link my app ,
because I'm not sure found recent version of this lib
I also use -lrt to prevent search some
On Tue, Sep 11, 2018, 13:10 Kurt Roeckx wrote:
> On Tue, Sep 11, 2018 at 04:59:45PM +0200, Juan Isoza wrote:
> > Hello,
> >
> > What is the better way, for anyone running, by example, Apache or nginx
> on
> > a popular Linux districution (Ubuntu, Debian, Suse
On 09/11/2018 02:35 PM, Viktor Dukhovni wrote:
On Tue, Sep 11, 2018 at 02:28:12PM -0400, Dennis Clarke wrote:
It sounds like a downstream ELF header nightmare.
Actually, it works just fine. You link with the variant library,
and it happily coexists with any dependencies you may have that in
On Tue, Sep 11, 2018 at 02:28:12PM -0400, Dennis Clarke wrote:
> >> It sounds like a downstream ELF header nightmare.
> >
> > Actually, it works just fine. You link with the variant library,
> > and it happily coexists with any dependencies you may have that in
> > turn depend on the system TLS
It sounds like a downstream ELF header nightmare.
Actually, it works just fine. You link with the variant library,
and it happily coexists with any dependencies you may have that in
turn depend on the system TLS library. The variant SONAME and
symbol versions provide all the requisite iso
On Tue, Sep 11, 2018 at 08:10:01PM +0200, Kurt Roeckx wrote:
> On Tue, Sep 11, 2018 at 04:59:45PM +0200, Juan Isoza wrote:
> > Hello,
> >
> > What is the better way, for anyone running, by example, Apache or nginx on
> > a popular Linux districution (Ubuntu, Debian,
On Tue, Sep 11, 2018 at 04:59:45PM +0200, Juan Isoza wrote:
> Hello,
>
> What is the better way, for anyone running, by example, Apache or nginx on
> a popular Linux districution (Ubuntu, Debian, Suse) and want support TLS
> 1.3 ?
>
> Waiting package update to have openssl 1
x86_64" ],
> >+shlib_variant => "-opt",
> >+},
> >+
I guess this is a thread about Linux, and I gave a BSD example, but
there are no substative differences.
> It sounds like a downstream ELF header nightmare.
Actually, it works just fine. You link wi
On 09/11/2018 01:09 PM, Viktor Dukhovni wrote:
On Sep 11, 2018, at 10:59 AM, Juan Isoza wrote:
What is the better way, for anyone running, by example, Apache or nginx on a
popular Linux districution (Ubuntu, Debian, Suse) and want support TLS 1.3 ?
Waiting package update to have openssl
> On Sep 11, 2018, at 10:59 AM, Juan Isoza wrote:
>
> What is the better way, for anyone running, by example, Apache or nginx on a
> popular Linux districution (Ubuntu, Debian, Suse) and want support TLS 1.3 ?
>
> Waiting package update to have openssl 1.1.1 ? prob
1 - 100 of 588 matches
Mail list logo
