On 30 Mar 2017, at 17:13, Florian Schmaus <[email protected]> wrote: > > On 30.03.2017 18:02, Dave Cridland wrote: >> On 30 March 2017 at 16:00, Florian Schmaus <[email protected]> wrote: >>> On 30.03.2017 15:54, Remko Tronçon wrote: >>>> On 30 March 2017 at 15:10, Andreas Straub <[email protected] >>>> <mailto:[email protected]>> wrote: >>>> You raise a valid point. I agree that this construction seems >>>> cleaner from a purely theoretical standpoint. >>>> >>>> Permissible implementations of XEdDSA may or may not emerge, but as long >>>> as it is not something available, you're taking a risk of making a >>>> standard that will never be adopted. >>>> … >>>> I agree that losing the audit is a downside, but I'm not sure if the >>>> alternative is realistic if you want your XEP to take off. >>> >>> I'm under the impression that OMEMO already took off. So I don't share >>> the concern that libsignal being GPL hinders adoption in any way.
>> The XSF does open standards, available to any implementer without >> restriction, not just GPL software. > > Erm? Nobody is disputing that. OMEMO is and will be an open standard > based on other open standards [1]. > > If I understood Remko correctly he is arguing that because there are no > non-GPL XEdDSA implementations OMEMO will probably not see any adoption. > Which I think is not true as the reality shows. > > Please correct me if I'm wrong. I think you are, yes. The concern has come from Remko’s comments about there being no non-libsignal implementations of the crypto primitives (and that no-one should be implementing those themselves) being met with something akin to “everyone should use libsignal”, which is suboptimal both on the front of libsignal being unusable for all but a small number of licenses (just GPL and AGPL, at a guess), and of needing a particular library being not great. OMEMO’s initial publication was delayed for some time, in large part because of the need to move away from a situation where it can only be practically implemented by using a single library. It’s a shame if we’ve still not resolved that adequately. /K _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
