Hello,
according to my understanding PJSIP is released under GPL and
proprietary licence. Since a few version there is a TLS implementation
that relies on OpenSSL, which features a 4-clause BSD and a Apache 1.1
GPL-incompatible licence. [1]
Right now this constitutes also a violation of the Debian DFSG. [2] It's
point #1 in "Serious violations (direct rejects even if we only find one
point)".
The usual workaround is to add a linking exception for OpenSSL to the
"offending" file but I believe that a more long term solution would be
to port the TLS code to GNUTLS, which is a LGPL-licensed project. [3]
This is preferred as it would allow statically linking the pjproject
libraries too (something that should be done even with the linking
exception). Alternatively there could be a second implementation relying
on GNUTLS that is enabled by default, letting OpenSSL active only upon
request (or for the proprietary distribution).
Do you think you could look into this?
Best,
Vittorio
[1] https://people.gnome.org/~markmc/openssl-and-the-gpl.html
[2] https://ftp-master.debian.org/REJECT-FAQ.html
[3] http://www.gnutls.org/
Through this message I come to kindly ask what is the status of this
issue?
I ask because it seems to be blocking other free/libre system
distributions too who wish to provide pjsip and free/libre software to
the users. And posing a licensing issue too so long as there is no way
to make pjsip choose GnuTLS by default (over OpenSSL).
I came to know this issue by means of a message in a bug report
([[https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843654#20]]), that
message talks about various patches that are made by GNU Ring to make
pjsip work according to their needs. As the message points out: there is
room for improvement because some things might have better ways to be
dealt with. The patches referenced by that message can be found by:
Downloading the latest release of Ring at
[[http://dl.ring.cx/ring-release/tarballs/]].
Extracting it.
Going to "ring-project/daemon/contrib/src/pjproject".
Last time I checked, the patches apply to pjproject 2.5.5 (to know that,
instead of going to "src", go to "tarballs"). Please
evaluate each patch and make corrections when needed.
The message was referenced in a discussion with GNU Ring
([[https://lists.gnu.org/archive/html/ring/2017-03/msg00009.html]]), in
which I explain my and Mx. Gradl's work on packaging GNU Ring (and
related dependencies, including pjsip/pjproject) to GNU Guix
([[https://lists.gnu.org/archive/html/guix-devel/2017-03/msg00867.html]]).
Hi all,
This message is just to let you know that due to a set of issues I
decided to give up on making and maintaining Guix recipes for GNU Ring
and all its dependencies (this includes pjproject/PJSIP). If you want
more information (also in case someone decides to continue the work),
please see [1].
[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30041.
--