jayf0s...@roadrunner.com said:
> I think I have tracked down the change in 1.1.1c that is causing this. It
> is the addition of the DEVRANDOM_WAIT functionality for linux in e_os.h and
> crypto/rand/rand_unix.c. lighttpd (libcrypto) is waiting in a select() call
> on /dev/random. ...
I
I also noticed that with 1.1.1b, the CFLAGS automatically included
'-Wall -O3', but with 1.1.1c, '-Wall -O3' is no longer included in the
CFLAGS. was this dropped? I added '-Wall -O3' to the CFLAGS, but this
did not seem to have any affect on the performance issue (unrelated?).
This is
Jay Foster wrote in <84571f12-68b3-f7ee-7896-c891a2e25...@roadrunner.com>:
|On 5/28/2019 10:39 AM, Jay Foster wrote:
|> I built OpenSSL 1.1.1c from the recent release, but have noticed what
|> seems like a significant performance drop compared with 1.1.1b. I
|> notice this when starting
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> Viktor Dukhovni
> Sent: Tuesday, May 28, 2019 14:21
>
> > On May 28, 2019, at 11:35 AM, Michael Wojcik
> wrote:
> >
> > Don't tell us about the ldd output. Show us. ldd output is short enough to
> include in an email
On 5/28/2019 10:39 AM, Jay Foster wrote:
I built OpenSSL 1.1.1c from the recent release, but have noticed what
seems like a significant performance drop compared with 1.1.1b. I
notice this when starting lighttpd. With 1.1.1b, lighttpd starts in a
few seconds, but with 1.1.1c, it takes
In general, this occurs because you have some other libraries (from your
system) that link against libcrypto.so.1.0.0. In theory, it should all just
work, but in practice I've often found my application did not work as
expected.
Specifically, I'd get a TLS end point that did not speak ECDSA
> On May 28, 2019, at 11:35 AM, Michael Wojcik
> wrote:
>
> Don't tell us about the ldd output. Show us. ldd output is short enough to
> include in an email message.
More useful than "ldd" output, is output from "readelf -d",
showing the NEEDED libraries, any RPATH, ...
--
Viktor.
Dennis Clarke wrote in :
|
|>> beta $ gzip -dc ../src/openssl-1.1.1c.tar.gz | tar -xf -
|>> tar: pax_global_header: typeflag 'g' not recognized, converting to
|>> regular file
|>> beta $
|>>
|>> Must be a gnu tar thing?
|>
|> Hi Dennis,
|>
|> it's not a bug, it's a feature. ;-)
|>
beta $ gzip -dc ../src/openssl-1.1.1c.tar.gz | tar -xf -
tar: pax_global_header: typeflag 'g' not recognized, converting to
regular file
beta $
Must be a gnu tar thing?
Hi Dennis,
it's not a bug, it's a feature. ;-)
No seriously: it's the `git archive` command which is used to export the
> -Ursprüngliche Nachricht-
> I don't thing I have seen this before :
>
> beta $ gzip -dc ../src/openssl-1.1.1c.tar.gz | tar -xf -
> tar: pax_global_header: typeflag 'g' not recognized, converting to
> regular file
> beta $
>
> Must be a gnu tar thing?
Hi Dennis,
it's not a bug, it's a
I don't thing I have seen this before :
beta $ gzip -dc ../src/openssl-1.1.1c.tar.gz | tar -xf -
tar: pax_global_header: typeflag 'g' not recognized, converting to
regular file
beta $
Must be a gnu tar thing?
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and
I built OpenSSL 1.1.1c from the recent release, but have noticed what
seems like a significant performance drop compared with 1.1.1b. I
notice this when starting lighttpd. With 1.1.1b, lighttpd starts in a
few seconds, but with 1.1.1c, it takes several minutes.
I also noticed that with
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> Chethan Kumar
> Sent: Tuesday, May 28, 2019 08:49
>
> I meant to say linking to both by doing ldd.
> When ldd is done on application, both libcrypto.so.1.0.0 and libcrypto.1.1 is
> shown.
Don't tell us about the ldd
I meant to say linking to both by doing ldd.
When ldd is done on application, both libcrypto.so.1.0.0 and libcrypto.1.1 is
shown.
Here libcrypto.so.1.0.0 is taken from the one provided by OS.
> Is it using some kind of dynamic module that happens to be linked with an
> older OpenSSL version?
In what way does it link to both? What output do you get when running
'ldd' in your application? Is it using some kind of dynamic module
that happens to be linked with an older OpenSSL version?
Cheers,
Richard
On Tue, 28 May 2019 06:59:27 +0200,
Chethan Kumar wrote:
>
>
> Dear all,
>
> Any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
OpenSSL version 1.1.1c 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.1c of our open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
OpenSSL version 1.1.0k 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.0k of our open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
OpenSSL version 1.0.2s 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.0.2s of our open
18 matches
Mail list logo
