-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rémy,
On 11/29/18 08:27, Rémy Maucherat wrote:
> On Sun, Nov 25, 2018 at 10:42 AM Rainer Jung
> wrote:
>
>> In our Java code, what happens is a call to unwrap() in
>> OpenSSLEngine. This call writes I think 146 bytes, then checks
>> pendingReadab
Am 29.11.2018 um 15:55 schrieb Mark Thomas:
On 29/11/2018 13:27, Rémy Maucherat wrote:
On Sun, Nov 25, 2018 at 10:42 AM Rainer Jung
wrote:
In our Java code, what happens is a call to unwrap() in OpenSSLEngine.
This call writes I think 146 bytes, then checks
pendingReadableBytesInSSL(). That c
On 29/11/2018 13:27, Rémy Maucherat wrote:
> On Sun, Nov 25, 2018 at 10:42 AM Rainer Jung
> wrote:
>
>> In our Java code, what happens is a call to unwrap() in OpenSSLEngine.
>> This call writes I think 146 bytes, then checks
>> pendingReadableBytesInSSL(). That call in turn calls SSL.readFromSSL
On Sun, Nov 25, 2018 at 10:42 AM Rainer Jung
wrote:
> In our Java code, what happens is a call to unwrap() in OpenSSLEngine.
> This call writes I think 146 bytes, then checks
> pendingReadableBytesInSSL(). That call in turn calls SSL.readFromSSL()
> and gets back "0" (from SSL_read()). Up in unwr
I've been looking at this in case we need a change in native before I
roll the 1.2.19 release.
On 25/11/2018 09:42, Rainer Jung wrote:
> I observed that when building tcnative against OpenSSL 1.1.1 I ran into
> hangs when talking TLS 1.0 with Tomcat trunk using that tcnative plus
> Nio(2).
>
> A
I observed that when building tcnative against OpenSSL 1.1.1 I ran into
hangs when talking TLS 1.0 with Tomcat trunk using that tcnative plus
Nio(2).
A simple "GET /" request eg. send with curl, hangs for 60 seconds after
a successful TLS handshake, then the client ends with an "empty reply
f
