linphone-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-developers] Where did the TLS support go from 3.6.1 to 3.7


From: KheOps
Subject: Re: [Linphone-developers] Where did the TLS support go from 3.6.1 to 3.7.0?
Date: Wed, 26 Mar 2014 23:42:05 +0000
User-agent: Mutt/1.5.23 (2014-03-12)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, Mar 26, 2014 at 04:47:54PM +0100, Ghislain MARY wrote:
> Hi,

Hi again,

> There are some configure options, but they are in the configure of the
> belle-sip SIP stack, not in the configure of Linphone ;-)
> So:
>  - build polarssl

This went well.

>  - build belle-sip enabling polarssl (it should enabled it automatically if
> it is found on the system)

I'm having troubles compiling belle-sip, but not related to polarssl.
As far as I understand, it may be related to antlr3 as I am getting very
similar error messages as described there, when compiling
libbellesip_generated_la-belle_sip_messageParser.lo:
http://osdir.com/ml/linphone-developers-sip-voip/2013-10/msg00021.html

First error messages I get are:
belle_sip_messageParser.c:9548:23: error: '_empty' undeclared here (not in a 
function)
     dfa1_T0, dfa1_T1, _empty, _empty

I have antlr 3.5. I can provide all the errors that 'make' produces, but
they are basically mostly the same as in the pastebin linked from the
abovementioned email: http://pastebin.com/kcdwv6Lg

I'll be thankful if you could provide me with any clue on how I could
solve this.

>  - build linphone

Went well with the belle-sip binary included in ArchLinux, so it should
be OK once I get to compile my own belle-sip.

> 
> Cheers,
> Ghislain

Thanks,
KheOps

> 
> On 26/03/2014 16:39, KheOps wrote:
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >
> >On Tue, Mar 25, 2014 at 02:02:37PM +0100, Ghislain MARY wrote:
> >>Hi,
> >>
> >>Linphone 3.7.0 no longer uses openssl. It uses polarssl instead:
> >>https://polarssl.org/
> >>It is possible that your distro ArchLinux do not package polarssl yet. But
> >>if you compile Linphone yourself, you should be able to make TLS work by
> >>compiling polarssl yourself.
> >Thanks a lot for the information. It is true that PolarSSL is not
> >(yet?) in the packages officially supported by ArchLinux.
> >
> >Is there anything particular to know in order to link Linphone against
> >PolarSSL? Or should I just have it installed and it will be detected
> >automagically? I instinctively expected some options in the 'configure'
> >script to specify the path etc. (just like with any other external lib).
> >
> >>Cheers,
> >>Ghislain
> >Best,
> >KheOps
> >
> >>On 25/03/2014 13:52, KheOps wrote:
> >>>-----BEGIN PGP SIGNED MESSAGE-----
> >>>Hash: SHA1
> >>>
> >>>Hello,
> >>>
> >>>I'm new to this list and subscribed because I'm having troubles in
> >>>trying to use TLS after switching from 3.6.1 to 3.7.0.
> >>>
> >>>I'm using linphone with the SIP service ostel.co and was able to
> >>>connect to it on port 5061 with TLS on 3.6.1 without problem.
> >>>
> >>>After switching to 3.7.0:
> >>>- - in the configuration dialog for my SIP account, the choice for
> >>>   Transport includes UDP and TCP but not TLS
> >>>- - I tried to write by hand "transport=tls" for the address of the SIP
> >>>   proxy
> >>>- - linphone does not even try to connect with this setting ; with the TCP
> >>>   transport (unencrypted), it connects fine to port 5060.
> >>>
> >>>I first thought this could be a problem specific to my distro
> >>>(ArchLinux) where the package maintainer had forgotten TLS support when
> >>>compiling the new version, so I downloaded the source to try to compile
> >>>it myself.
> >>>
> >>>I then noticed that the "configure" script did not have any option
> >>>related to TLS or SSL anymore, whereas it had the --enable-ssl option
> >>>and OpenSSL linker and compiler flags variables in the 3.6.1 version of
> >>>the source.
> >>>
> >>>Additionally, on ArchLinux, /usr/lib/liblinphone.so.5.0.0 (linphone
> >>>package 3.6.1) is linked against libssl, which is not the case for
> >>>/usr/lib/liblinphone.so.6.0.0 (linphone package 3.7.0).
> >>>
> >>>I would highly appreciate some help on this, has not having the TLS
> >>>support is an important privacy issue for me.
> >>>
> >>>Thank you,
> >>>KheOps
> >>>-----BEGIN PGP SIGNATURE-----
> >>>Version: GnuPG v2.0.22 (GNU/Linux)
> >>>
> >>>iQEcBAEBAgAGBQJTMXwaAAoJEK9g/8GX/m3dZKAH/iQsvODACHgU092DvJSjBirs
> >>>Sb0YKZ7AkEcRw7rLthsZGhAEXZ1G2tFjrPwpsqy1TlxsgXx2wAuhowyrkRs9URi2
> >>>F+krt+EtzR2xeMgNwlqqPbDWx/TQhZQ6Q/p2+eF27K5jBQvBUoWa919jTXRnW8rJ
> >>>4Dc/zJwAoDW1oA2wIqfaujB871HyjxMAnF6ivvDghn4Cc6AC455NX03r8y8DNm9g
> >>>JP/w3iqHgU7c+htqQl8fhbd2Py7fjdkXi2eKANVX9hdrIWuY/pGrmjYtIcnfutjI
> >>>ZYnr3rOh34mGPXSA/nXQIVAFkPmqSSRdbrP1AimCVuE2gBibMa2kS2S2ucnTZxc=
> >>>=XBtL
> >>>-----END PGP SIGNATURE-----
> >>>
> >>>_______________________________________________
> >>>Linphone-developers mailing list
> >>>address@hidden
> >>>https://lists.nongnu.org/mailman/listinfo/linphone-developers
> >>
> >>_______________________________________________
> >>Linphone-developers mailing list
> >>address@hidden
> >>https://lists.nongnu.org/mailman/listinfo/linphone-developers
> >-----BEGIN PGP SIGNATURE-----
> >Version: GnuPG v2.0.22 (GNU/Linux)
> >
> >iQEcBAEBAgAGBQJTMvTEAAoJEK9g/8GX/m3dPSsH/0rID6YoZ1dVRhJvUNPLnzVS
> >HSBVsuJHTN+/UlF4UEsoFbr7I7MOBUxLtiLD+MMeGeS7SNa1cSRbnbc8VqjIIRfU
> >xtueaSGNce3ccQIRtJNcrRI2k+OGpDFBTKeDcYGGC+T1AHiRzkhpIuEYeZmGSwyG
> >blnlS+sPHU93waGSyd0A62eXyVzHl2ekBTcaywFYe27EkZKSikSQql6BjXKwWEJG
> >yOeMw0P/Q5S6wrrjsWBnZKidPxq7vbizUWfe30NoNXeohf0aqbbVa8jHNBAhJvVx
> >Q4/J/Ewxz1pS1EHdIdAqaX7VU9ipu+p3SMI7EFDldsoSHH5wpA779k4JmgvfMtg=
> >=hfjN
> >-----END PGP SIGNATURE-----
> >
> >_______________________________________________
> >Linphone-developers mailing list
> >address@hidden
> >https://lists.nongnu.org/mailman/listinfo/linphone-developers
> 
> 
> _______________________________________________
> Linphone-developers mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/linphone-developers
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJTM2XNAAoJEK9g/8GX/m3dLNIIAKFDunBauW6+7E6PmbSVMJZf
dK7ngE1JJrnoMWeEizhOFFHwCIy2OLTDsUwf72V/PNUz9Gf6R2HMA/wtHa7pyQMl
4W1o4JDBJes2hNbW+mU67v2JgPge15OdNGtOQI/AlJb4wn5fI01zaRG95Rc8u1a4
3aWHg1yF/76JCLMW8g2KO0F/Qq5xfKeL3xWCP0oiKqf4taasApGMOWzjGnljJRWN
w3aWOZQBT2aGF5dziMTY8FGuLDtejmRpIa6fJtOZdOGInkpTh6N0ZSPVEzWWquwd
xbYBl2eXd+Fm+DeY8rtHA7VaBr95uP0iY65Vx7VRGs3PpIdobK6UoOrWEzazszk=
=ZFXV
-----END PGP SIGNATURE-----



reply via email to

[Prev in Thread] Current Thread [Next in Thread]