This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Maintainers of CURL, MUTT, PYTHON and WGET, heads up!

Yes, I checked an actual SSL connection. It actually worked ;-)

There's no call anywhere in the source to SSLeay or SSLeay_version.
There are some references to the value of both SSLEAY_VERSION_NUMBER and
OPENSSL_VERSION_NUMBER. It's not assigned (set) anywhere in curl's code,
just used. I do see ">=" types of comparisons (as opposed to checking
for specific version #'s), so I assume he's golden in that regard.

I will try to get the upstream folk to change the behavior so it uses
SSLeay_version() sometime in the future...

Thanks for the info.

-----Original Message-----
From: Corinna Vinschen []
Sent: Tuesday, January 15, 2002 12:46 PM

On Tue, Jan 15, 2002 at 12:39:39PM -0500, Roth, Kevin P. wrote:
> ... However, curl
> outputs the openssl version as part of its --version output, and it
> still says openssl 0.9.6b! ...

Look into the source.  If there's a call to SSLeay() or
SSLeay_version() it takes the version it's running under.

grep for OPENSSL_VERSION_NUMBER.  If it's just used as
is in a printf() somewhere, curl reports the version
it's linked against.

The second is bad style.  It should print either the current
version using one of the above calls or it should report both
versions, the linked and the current one.

Anyway, it's good to hear that it still works.  You checked
an SSL connection?

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]