[License-discuss] Discussion: AGPL and Open Source Definition conflict

[Bruce Perens]

On the side of the person needing to comply, one need only make sure the
source code is carefully published. On the side of the person wishing to
access the source code, the only alternative is to turn on logging or use a
hacked client. I don't think it would be permissible to emit no notice
regarding the source code at all simply because the protocol doesn't make
it easy to read.

On Thu, Aug 15, 2019 at 3:43 AM Kevin P. Fleming <kevin+osi at km6g.us> wrote:

> Bruce's point about the
> information being visible in the network traffic was considered in our
> discussions, but then we realized that any implementation which used
> SIPS (SIP over TLS, analogous to HTTPS) would mean that the
> information would *not* be visible in the network traffic; it would
> only be visible inside the client software after decryption.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20190924/7cafdd97/attachment.html>