Chethan Kumar wrote:
> Sorry for the inconvenience caused by not asking query clearly.
> Below is the output from ldd on application.
Right, and now you need to recursively go through the list with readelf or
ldd, and which out which one of these libraries then requires
libcrypto.1.0.0.
> On May 29, 2019, at 9:43 AM, Michael Wojcik
> wrote:
>
> So either the application program depends on libcrypto.so.1.0.0, or one of
> the preceding libraries does. Some path through the dependency graph leads to
> libcrypto.so.1.0.0.
Not only is the application (dynamically) linked
> From: Chethan Kumar [mailto:chethan.ku...@toshiba-tsip.com]
> Sent: Wednesday, May 29, 2019 04:07
>
> Below is the output from ldd on application.
> Seriously I didn't knew application uses these many libraries[Knew only the
> problem].
> linux-gate.so.1 (0xf76fc000)
>
is needed to resolve the problem.
Thanks in advance,
Chethan
-Original Message-
From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
Michael Wojcik
Sent: Wednesday, May 29, 2019 2:52 AM
To: openssl-users@openssl.org
Subject: RE: Application linking to both libcrypto.so.1.0.0 and
> 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
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.
> 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
e
Sent: Tuesday, May 28, 2019 7:37 PM
To: openssl-users@openssl.org
Subject: Re: Application linking to both libcrypto.so.1.0.0 and libcrypto.so.1.1
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 h
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
Dear all,
Any help for the below query would be appreciated.
Thanks in advance,
Chethan Kumar
From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
Chethan Kumar
Sent: Wednesday, May 22, 2019 11:35 AM
To: openssl-users@openssl.org
Subject: Application linking to both
11 matches
Mail list logo
