On Wed, Jun 20, 2018 at 8:29 PM, Yann Ylavic wrote:
>
> Since it happens with s_client <=> s_server (no third party), maybe
> someone can ask the openssl team why?
I just asked on their users@ list:
https://mta.openssl.org/pipermail/openssl-users/2018-June/008229.html
On Fri, Jun 15, 2018 at 10:03 PM, Dennis Clarke wrote:
>
> Seems to issue "read R BLOCK" twice for some odd reason.
Indeed, same here/
>
> A closer look with "-state -debug" reveals that we get multiple
> "SSL_connect:SSL negotiation finished successfully" before ever
> accepting a GET/POST/FOO
On 06/17/2018 04:35 PM, Apache Lounge wrote:
Same behavior "read R BLOCK" twice on Windows with trunk from today
(1833659):
Clearly there is a loop somewhere which is happening twice and may be
because of some state variable not set corrected on entry to the loop.
Difficult to trace.
Same behavior "read R BLOCK" twice on Windows with trunk from today
(1833659):
On Friday 15/06/2018 at 22:03, Dennis Clarke wrote:
Thank you Yann Ylavic !
Sure enough no patch was needed and trunk compiles up neatly and just
a
bit noisey about a few odd warnings ... nothing too
Thank you Yann Ylavic !
Sure enough no patch was needed and trunk compiles up neatly and just a
bit noisey about a few odd warnings ... nothing too interesting.
So then ... as I reported earlier I can get reasonable handshake and
TLSv1.3 traffic with cipher TLS_AES_128_GCM_SHA256 from the
