Hi Matt,
Thanks for the response,
I added a log as suggested by you. I don't see the call entering the above
mentioned code block.
Logs on server side:
[10/15/0117 10:34:43] 803F1700 Link-2 (SSL_accept) Failed to accept
new connection, Socket Id 65, Return Value 1
[10/15/0117 10:34:43]
(This is for the regular OpenSSL 1.0.2, not 1.1.x):
As I build OpenSSL for various embedded or semi-embedded (mobile)
platforms, I have run into the basic issue of how to run the equivalent
of "make test" when the code is compiled for an embedded platform that
is neither self-hosting (so make, co
I'm updating our Delphi SSL code to support 1.1.1 in addition to 1.0.2
and 1.1.0, common code with a few version checks. This is using Windows
10.
With 1.1.1, SSL connections fail to initialise, failing with the first
BIO_read after setting up the context and BIOs. There is no real error
(I can
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> Grace Priscilla Jero
> Sent: Wednesday, November 15, 2017 09:42
> To: openssl-users@openssl.org
> Subject: Re: [openssl-users] Supported cipher suites
> Some of them that we tried does not work. Is there any additiona
Hello Fabrizio,
actually the whole private key and all its components are not loaded with
ENGINE_load_private_key. Only a part of them (modulus and public exponent).
These components are enough to, for example, make a key/certificate match
verification.
Once a private key operation is needed
On 16/11/17 07:00, Viktor Dukhovni wrote:
> In the upcoming TLS 1.3 the ciphers are completely different from
> previous versions, and configuration via cipher strings was not
> implemented last I looked. This may have changed...
You have always been able to configure the TLSv1.3 ciphers via ci
