bug in 3.0.18: gnutls-cli fails to transfer data to gnutls-serv --echo

[Alexandre Bique]

On Thu, Apr 19, 2012 at 17:34, Nikos Mavrogiannopoulos <nmav at gnutls.org> wrote:
> On Thu, Apr 19, 2012 at 4:00 PM, Alexandre Bique
> <bique.alexandre at gmail.com> wrote:
>
>>> I see a renegotiation request there and gnutls-serv doesn't do that,
>>> so it might be that.
>> So in production code, do I have to check gnutls_record_{send,recv}
>> return value to manually start a renegotiation or re-handshake?
>
> It depends on what you want to do. A server isn't obliged to renegotiate
> just because the client asked. I don't know why openssl s_client asked
> for renegotiation in your example.

Ok.

>> Could we add renegotiation to gnutls-serv?
>
> Now that I check it, it does support renegotiation. I cannot check the
> issue soon, but you can check the debugging output of gnutls-serv
> using -d 9 or so.

Here the last line on stderr:

|<2>| ASSERT: gnutls_record.c:366
Error while sending data
|<4>| REC[0x121ae30]: SSL 3.2 Application Data packet received. Epoch
0, length: 8240
|<4>| REC[0x121ae30]: Expected Packet Application Data(23)
|<4>| REC[0x121ae30]: Received Packet Application Data(23) with length: 8240
|<2>| ASSERT: gnutls_buffers.c:494
|<2>| ASSERT: gnutls_record.c:1002
|<2>| ASSERT: gnutls_record.c:1204
|<4>| REC[0x121ae30]: SSL 3.2 Application Data packet received. Epoch
0, length: 8240
|<4>| REC[0x121ae30]: Expected Packet Application Data(23)
|<4>| REC[0x121ae30]: Received Packet Application Data(23) with length: 8240
|<2>| ASSERT: gnutls_buffers.c:482
|<2>| ASSERT: gnutls_record.c:1002
|<2>| ASSERT: gnutls_record.c:1204
|<2>| errno: 32
|<2>| ASSERT: gnutls_buffers.c:374
|<2>| ASSERT: gnutls_buffers.c:599
|<2>| ASSERT: gnutls_record.c:201
|<4>| REC[0x121ae30]: Start of epoch cleanup
|<4>| REC[0x121ae30]: End of epoch cleanup
|<4>| REC[0x121ae30]: Epoch #1 freed

And on stdout I got:

Error: The specified session has been invalidated for some reason.
Error: The specified session has been invalidated for some reason.
Error: The specified session has been invalidated for some reason.
Error: The specified session has been invalidated for some reason.
Error: The specified session has been invalidated for some reason.
Error: The specified session has been invalidated for some reason.
Error: The specified session has been invalidated for some reason.
Error: The specified session has been invalidated for some reason.
Error: The specified session has been invalidated for some reason.
Error: The specified session has been invalidated for some reason.
Error: The specified session has been invalidated for some reason.
Error: The specified session has been invalidated for some reason.
Error: The specified session has been invalidated for some reason.
Error: The specified session has been invalidated for some reason.
Error: The specified session has been invalidated for some reason.
Error: The specified session has been invalidated for some reason.
...

-- 
Alexandre Bique