----- Original Message ----- > From: "Tristan Matthews" <[email protected]> > To: "James Le Cuirot" <[email protected]> > Cc: [email protected] > Sent: Monday, November 3, 2014 10:16:54 AM > Subject: Re: [SFLphone] Invalid certificate detected? > > ----- Original Message ----- > > From: "James Le Cuirot" <[email protected]> > > To: "Emmanuel Lepage" <[email protected]> > > Cc: [email protected], "Tristan Matthews" > > <[email protected]> > > Sent: Monday, November 3, 2014 10:14:10 AM > > Subject: Re: [SFLphone] Invalid certificate detected? > > > > Hi Emmanuel, Tristan, > > > > After much testing with the latest nightly today, I've been able to > > attribute most of the problems to user error. I now have the latest > > nightly successfully connecting over TLS. > > Great! > > > > > The hangs and missing accounts were due to the daemon process > > segfaulting and that was clearer once I ran it separately. The one > > bug I can definitely identify out of this is that not setting the > > private key file causes the daemon to segfault, even when first > > starting SFLphone after an upgrade. > > OK we will try and fix that ASAP.
Would it be possible to get a backtrace for this? See https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details for info. Best, Tristan > > > > > sipaccount.cpp:1206:0x7bc0: Using 6 ciphers > > siptransport.cpp:299:0x7bc0: Creating TLS listener {TLS transport > > on > > default:5061} on 0.0.0.0:5061... > > sipaccount.cpp:821:0x7bc0: Creating transport > > siptransport.cpp:331:0x7bc0: getTlsTransport host pbx.test.com > > resolved to -> 192.168.1.49:0 > > siptransport.cpp:337:0x7bc0: Get new TLS transport to > > 192.168.1.49:5061 > > sipaccount.cpp:757:0x7bc0: doRegister > > siptransport.cpp:279:0x7bc0: Created UDP transport on default : > > 0.0.0.0:5060 > > Warning: built with video support > > Segmentation fault (core dumped) > > > > Thanks for your help, > > James > > Thanks for the detailed info, we will let you know when it's fixed. > > Best, > Tristan > > > > > > > On Thu, 30 Oct 2014 12:10:00 -0400 (EDT) > > Emmanuel Lepage <[email protected]> wrote: > > > > > Hello James, > > > > > > The invalid certificate popup is just a warning, you can still > > > accept > > > the certificate regardless or its perceived validity. > > > > > > This message is being rewritten to be clear and unambiguous. This > > > work wont be in the nightly until at least 2 weeks. The reason > > > for > > > the message should be present in the daemon debug logs. You can > > > get > > > them by invoking: > > > > > > /usr/lib64/sflphone/sflphoned -c -d > > > > > > Please note that all clients need to be closed first or this > > > command > > > will fail. > > > > > > If you still cannot connect you your TLS target, please give us a > > > copy of this log by replying to me or Tristan. Make sure you > > > first > > > remove any sensitive information. > > > > > > Regards, > > > Emmanuel Lepage > > > > -- > > Tristan Matthews > Développeur de logiciels libres > [email protected] > Ligne directe: 514-276-5468 poste 190 > > Fax : 514-276-5465 > 7275 Saint Urbain > Bureau 200 > Montréal, QC, H2R 2Y5 > > _______________________________________________ > SFLphone mailing list > [email protected] > http://lists.savoirfairelinux.net/mailman/listinfo/sflphone > -- Tristan Matthews Développeur de logiciels libres [email protected] Ligne directe: 514-276-5468 poste 190 Fax : 514-276-5465 7275 Saint Urbain Bureau 200 Montréal, QC, H2R 2Y5 _______________________________________________ SFLphone mailing list [email protected] http://lists.savoirfairelinux.net/mailman/listinfo/sflphone
