Hi Tristan, On Thu, 30 Oct 2014 10:31:18 -0400 (EDT) Tristan Matthews <[email protected]> wrote:
> ----- Original Message ----- > > From: "James Le Cuirot" <[email protected]> > > To: [email protected] > > Sent: Thursday, October 30, 2014 8:26:06 AM > > Subject: [SFLphone] Invalid certificate detected? > > > > Bonjour, > > > > We have just updated from SFLphone 1.3.0 to 1.4.1 on Fedora 20. We > > were > > using TLS authentication, admittedly just testing it out at the > > moment, > > but it stopped working after the update. When I now select the > > public endpoint certificate, it says "Invalid certificate detected" > > due to task #44946 and fails to authenticate if I use it anyway. The > > certificate worked before so why is it invalid now? The error is > > very vague so I have little to go on. The only significant thing I > > can say about it is that it's self-signed. Any ideas? > > TLS was broken due to a regression in 1.4.1: see > https://projects.savoirfairelinux.com/issues/53057 This has since > been fixed but we haven't made a release with this fix yet. I'm not sure if that's the same issue. We've added TLS to a separate account rather than IP2IP. I just tried the latest nightly but it still says "Invalid certificate detected" and registering seems to hang. After I restart SFLphone, both accounts are gone. It also seems to complain about D-Bus a lot. :| Regards, James _______________________________________________ SFLphone mailing list [email protected] http://lists.savoirfairelinux.net/mailman/listinfo/sflphone
