[reSIProcate] WSS with AfterSocketCreationFunction causes core

[Scott Godin]

Inspecting the TLS handshake and TCP rst packets in wireshark should help
shed some light.  At least you will be able to see which side is
terminating the connection.

Scott

On Tue, Jun 25, 2013 at 1:47 PM, Nathan Stratton <nathan at robotics.net>wrote:

> On Mon, Jun 24, 2013 at 3:03 PM, Daniel Pocock <daniel at pocock.com.au>wrote:
>
>>
>>
>> I notice it refers to TLS error code 5 which is ERR_LIB_DH from
>> openssl/err.h
>>
>> The next line seems to say the same thing:
>>
>> error:00000005:lib(0):func(0):DH lib
>>
>> I don't know the internals of TLS and OpenSSL in depth, but my first
>> guesses:
>>
>> - it might be triggered by something in your cipher spec or other TLS
>> settings - do you have any non-standard config for TLS init?
>>
>
> Don't believe so.
>
>
>> - your server certificate - how did you generate it?  Are you using a
>> self-signed cert for testing.
>>
>
> They are 5 year valid COMODO certs via PositiveSSL.
>
>
>> - your OpenSSL version - I think I remember you are on RHEL with EPEL -
>> could you check the OpenSSL version and consider trying a version of
>> OpenSSL from Fedora?  EPEL doesn't always have the latest versions of
>> things.
>>
>
> I have tried upgrading, currently running 1.0.1e
>
> --
> ><>
> Nathan Stratton                                               Founder, CTO
> Exario Networks, Inc.
> nathan at robotics.net                                     nathan at
> exarionetworks.com
> http://www.robotics.net
> http://www.exarionetworks.com/
>
> Building the WebRTC solutions today that your customers will demand
> tomorrow.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20130625/25046a6d/attachment.htm>