[OTR-dev] OTR-dev Digest, Vol 39, Issue 2

Chris Ballinger chrisballinger at gmail.com
Wed May 2 14:17:42 EDT 2012


When writing ChatSecure I followed the logic in this post on StackOverflow:
http://stackoverflow.com/a/1321681/805882

Since I distribute the object files in question with the app (and my app is
open source) I feel that I don't violate the spirit of the LGPL. However,
I'm not a lawyer, and I know that some FSF devotees would disagree with me.

I have been considered reimplementing libotr in Objective-C and licensing
it under BSD as well, but I wanted to wait until after libotr4 / OTRv3 was
released. I have had some interest from another developer looking to fund a
rewrite of libotr to use the iOS Common Crypto routines. Maybe we could all
work together.

On Wed, May 2, 2012 at 10:36 AM, Hans-Christoph Steiner <
hans at guardianproject.info> wrote:

>
> On May 2, 2012, at 10:38 AM, Nathan of Guardian wrote:
>
>  On 05/02/2012 09:08 AM, Hans-Christoph Steiner wrote:
>
> I guess that doesn’t make a lot of sense imho. It won’t be usable in the Mac or iOS AppStores due to licensinc constraints of the (L)GPL. I’m currently looking for helping hands and some sponsoring to natively reimplement libotr in Objective-C under a BSD license.
>
>  I would look at what Chris has already done here:
> https://github.com/chrisballinger/Off-the-Record-iOS
>
>
> Careful, that uses a few (L)GPL'ed libraries like libgcrypt and libotr, so
> putting that code into the Apple App Store is in violation of the terms of
> the (L)GPL since the Apple App Store Terms conflict with the GPL.
>  Distributing GPL software for iOS outside of the App Store is totally
> clear in terms of the GPL.
>
> .hc
>
> _______________________________________________
> OTR-dev mailing list
> OTR-dev at lists.cypherpunks.ca
> http://lists.cypherpunks.ca/mailman/listinfo/otr-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cypherpunks.ca/pipermail/otr-dev/attachments/20120502/d0d2066c/attachment.html>


More information about the OTR-dev mailing list