Am 31.03.20 um 09:14 schrieb Tom van Leeuwen:
> From: Tom van Leeuwen
>
> When a client disconnects from a server compiled with mbedTLS, the server
> cannot process the PUSH_REQUEST from a new connection with the same client
> IP and port number. This is the case when the client binds to a
From: Tom van Leeuwen
When a client disconnects from a server compiled with mbedTLS, the server
cannot process the PUSH_REQUEST from a new connection with the same client
IP and port number. This is the case when the client binds to a static port.
This behavior is initiated by move_session(),
Hi Tom,
you forgot to CC the mailing list :-)
I am adding it back.
On 24/03/2020 16:44, Tom van Leeuwen wrote:
> On 24-03-2020 14:54, Antonio Quartulli wrote:
>> Hi,
>>
>> On 24/03/2020 14:35, Gert Doering wrote:
>>> Hi,
>>>
>>> On Tue, Mar 24, 2020 at 11:42:02AM +0100, Tom van Leeuwen wrote:
Hi,
On 24/03/2020 14:35, Gert Doering wrote:
> Hi,
>
> On Tue, Mar 24, 2020 at 11:42:02AM +0100, Tom van Leeuwen wrote:
>> When an mbedTLS session is moved in move_session(), the contents of the
>> the tls_session is copied to the new session and the old session is
>> reinitialized. This
Hi,
On Tue, Mar 24, 2020 at 11:42:02AM +0100, Tom van Leeuwen wrote:
> When an mbedTLS session is moved in move_session(), the contents of the
> the tls_session is copied to the new session and the old session is
> reinitialized. This tls_session contains, amongst other things, an
>
When an mbedTLS session is moved in move_session(), the contents of the
the tls_session is copied to the new session and the old session is
reinitialized. This tls_session contains, amongst other things, an
mbedtls_ssl_config and bio_ctx structure. However, the mbedtls context has
internal
