On Sep 1, 2017, at 18:48, Matt Caswell wrote:
>>> *Subject:* *openssl 1-1-0-stable fails*
>>>
>>> OpenSSL_1_1_0-stable current Github
>>>
>>> Test Summary Report
>>> ---
>>> ../test/recipes/80-test_cms.t(Wstat: 256 Tests: 4 Failed: 1)
>>> Failed test: 4
>>> Non-zer
On 01/09/17 23:42, Blumenthal, Uri - 0553 - MITLL wrote:
>
>
> Begin forwarded
>
>> *Subject:* *openssl 1-1-0-stable fails*
>>
>> OpenSSL_1_1_0-stable current Github
>>
>> Test Summary Report
>> ---
>> ../test/recipes/80-test_cms.t(Wstat: 256 Tests: 4 Failed: 1)
>>
Begin forwarded
> Subject: openssl 1-1-0-stable fails
>
> OpenSSL_1_1_0-stable current Github
>
> Test Summary Report
> ---
> ../test/recipes/80-test_cms.t(Wstat: 256 Tests: 4 Failed: 1)
> Failed test: 4
> Non-zero exit status: 1
> Files=95, Tests=561, 165 wal
FWIW, there’s a ‘libtls’ library from the libre folks that might be worth
looking at.
If you come up with useful snippets we can start by posting them to the wiki,
for example
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
On 29.08.2017 16:15, Salz, Rich via openssl-dev wrote:
>> Getting the client connect right appears surprisingly messy when one
>> needs to cope with all kinds of network error situations including
>> domain name resolution issues and temporarily unreachable servers.
>> Both indefini
When openssl sends a second Client Hello message, it modifies it quite
extensively, not only client_random is changed but also advertised cipher
suites.
see https://github.com/openssl/openssl/issues/4292
That makes it non-compliant with the current draft (-21):
When a client first connects
