News for hackers. Stuff that matters.
Re:Krypton: phone-based U2F Authenticator by CiPHPerCoder on Thursday August 30, 2018 @01:36PM (#17878781)
Re:Krypton: phone-based U2F Authenticator by CaliforniaKarl on Thursday August 30, 2018 @01:38PM (#17878802)
Their CONTRIBUTING file does say "We are currently researching what type of license makes the most sense for Kryptonite." On the other hand, that file was last updated on `master` in January 2017.
Re:Krypton: phone-based U2F Authenticator by thrillgore on Thursday August 30, 2018 @03:49PM (#17880112)
Someone paid attention to what Redislabs did, and wanted to get ahead of it. In the most ass way possible.
Re:Krypton: phone-based U2F Authenticator by ramses0 on Thursday August 30, 2018 @06:20PM (#17881312)
Open Source != Free Software.

"Free as in beer, not as in speech."

You're welcome to pick your own license / source availability terms for your own work.

Re:Krypton: phone-based U2F Authenticator by type0 on Friday August 31, 2018 @07:57AM (#17884779)
Both are source available software [0], other than that you can't compare them. Krypton is fully proprietary nothing more nothing less, what RedisLabs did was a complete disservice to the whole open source phenomena without addressing any actual business concerns. They misinterpreted the whole clause thing to somehow say that your software can be both open and closed at the same time (it can't). They could at least had maybe done a minimal research and maybe learned somethings from Suns community source SCSL [1] or other similar liceses from the past and they even didn't bother doing that (the irony that SCSL is now hosted at Oracle speaks for itself).

[0] https://en.wikipedia.org/wiki/Source-available_software [1] https://www.oracle.com/technetwork/java/scsl-1-1-149938.txt