On 2024-06-13, R.Wieser <
[email protected]d> wrote:
0x14077410 - SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake
failure
I've encountered a similar problem. As far as I can ascertain, it means
that the server is making a non-TLS response to a TLS handshake.
Hmmm... My (ancient) FireFox browser has no problem with accessing the same site, making me assume its something on my end that goes wrong. Any idea what it might be and/or how to fix - Or even just how I can pin-point - it ?
You might be trying to establish a TLS 1.1 connection to a server that
wants TLS 1.3.
Version 1.0.2 is pretty old. Try a newer version; they're up to 3.3.1
now.
Any chance you know of a website where they have pre-compiled DLLS for download and mention which version of Windows it needs - and preferrable
have (links to) information/tutorials/example-code about how to use those DLLs ? (Having to spend multiple hours scouring the 'intarwebz' for even just headerfiles has become less-and-less appealing).
In a word, no. Besides, not being a fan of DLLs, I was looking for
a way to build modules I could statically link, using a compiler of
my choosing. Although I had managed to build 1.0.1g with the Borland
C++ Builder 5.5 I've been using to build all my software, I had to
switch to MinGW to build version 3.x of libcrypto.a and libssl.a -
and then, of course, I had to change my makefiles to compile the
calling programs with MinGW as well.
It's a lot of work. Take a close look at
https://www.openssl.org
and be prepared to use your favourite search engine a lot.
Under Linux it's _so_ much easier - everything is built in.
--
/~\ Charlie Gibbs | The Internet is like a big city:
\ / <
[email protected]d> | it has plenty of bright lights and
X I'm really at ac.dekanfrus | excitement, but also dark alleys
/ \ if you read it the right way. | down which the unwary get mugged.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)