wrote:
>
>
> On 18/09/16 01:01, Chad Phillips wrote:
> > On Sat, Sep 17, 2016 at 3:43 PM, Matt Caswell > <mailto:m...@openssl.org>> wrote:
> >
> > There is an OpenSSL API which is intended to resolve this issue:
> >
> > DTLSv1_handle_timeou
On Sat, Sep 17, 2016 at 3:43 PM, Matt Caswell wrote:
There is an OpenSSL API which is intended to resolve this issue:
>
> DTLSv1_handle_timeout()
>
> The application is expected to call this periodically during the
> handshake if no other data has been sent or received. The causes
> OpenSSL to ch
Matt, thanks for the reply, very helpful so far! Answers to your questions
below:
You don't say what version of OpenSSL.
>
The support library I’m using is Licode:
http://lynckia.com/licode/index.html
The version of openssl I have compiled into it is 1.0.2h.
> The packet trace you sent is quit
I’m using a support library leveraging openssl to complete a DTLS handshake.
Occasionally, I’ll see in my packet captures that a handshake has failed
with a “Certificate reassembly error”, and the support library doesn’t seem
to be catching this properly to forward the error on.
The library devel
Wondering if anyone can recommend a consultant.
I'm having a very specific problem with a lower-level WebRTC library that
I'm unable to fix myself. I have plenty of debugging information, and am
pretty sure it's due to an improperly handled DTLS handshake failure.
Ideally, it would be someone wh
