How are you guys going to get Cryptocat on the iPhone app store? Apple rejects GPL-licensed apps.
Is that the case? I thought it was more that the GPL rejects distribution on the App Store.
Cryptocat for iPhone and Android – Call for Review
81–84 of 84 posts
Re: Cryptocat for iPhone and Android – Call for Review
#82Earlier quoted context omitted.
It's true that we don't have a research paper per se for the multiparty protocol, but we do have a specification document [1] as well as implementations in Objective-C, Java and JavaScript. The specification, as well as the implementations, have received both professional audits (from cryptographers) as well as community audits. The reason we don't have a research paper published is simply because we're working on on…
> as well as implementations in Objective-C, Java and JavaScript. Factor the ObjC version out to plain C, and call into it from your Objective C implementation. Make the plain C version the canonical version. (Things like Emscripten may be useful here for your JS use-case.) This is how libotr does it, and for good reason. Then, others can use it, and perhaps you will get meaningful free auditing. What you're doing no…
Re: Cryptocat for iPhone and Android – Call for Review
#83How are you guys going to get Cryptocat on the iPhone app store? Apple rejects GPL-licensed apps.
If they own the copyright they can also release it under the 'whatever terms are appropriate for the app store licence'.
Re: Cryptocat for iPhone and Android – Call for Review
#84Earlier quoted context omitted.
If they own the copyright they can also release it under the 'whatever terms are appropriate for the app store licence'.
I thought the GPL automatically gives all rights to the code to the FSF.
GPL is a copyright license, which people who receive it can use as permission when redistributing the copyrighted work.
The GPL do not give FSF anything. Same is true for example that Massachusetts Institute of Technology do not get all the rights when some code is licensed under MIT license.