News for hackers. Stuff that matters.
Re:Krypton: phone-based U2F Authenticator by jrockway on Thursday August 30, 2018 @01:33PM (#17878753)
What is the business model here? They release what they purport to be their source code on Github, but under a license that prohibits ... everything (literally the words "All Rights Reserved"). So clearly they want to sell that, and then have the open source community debug it for them for free, which I just don't see happening. With no way to validate that the source code on Github is what ends up in their compiled binaries, I don't see the value to anyone.
Re:Krypton: phone-based U2F Authenticator by xpaulbettsx on Thursday August 30, 2018 @01:40PM (#17878830)
If anything, a commercial security product that allows anyone to audit the source code seems like a pretty Useful Pattern
Re:Krypton: phone-based U2F Authenticator by dsr_ on Thursday August 30, 2018 @02:02PM (#17879055)
...only if you can prove that the source code you show them builds the binary that you install, every single time.
Re:Krypton: phone-based U2F Authenticator by jgalt212 on Thursday August 30, 2018 @02:50PM (#17879599)
or you can compile it yourself, or am missing something from you comment?
Re:Krypton: phone-based U2F Authenticator by solatic on Friday August 31, 2018 @01:27AM (#17883175)
If all rights are reserved on the original source code, then compiling the source code can be construed as intent for intellectual property theft, since the right to compile the code was never expressly given to you.

Looking at all-rights-reserved code on a public repository on GitHub is like going to a strip club - you may look, but you can't touch.

Re:Krypton: phone-based U2F Authenticator by desdiv on Friday August 31, 2018 @10:55AM (#17886063)
Then it's a good thing that they made clarifications in their FAQ:

>Feel free to compile Krypton from source and run it on your phone and workstation. [0]

[0] https://krypt.co/faq/

Re:Krypton: phone-based U2F Authenticator by mattpavelle on Thursday August 30, 2018 @03:26PM (#17879917)
Right. You could also compile it yourself with the same chainset / toolset the Krypton folks use and compare the binaries. There's probably a way to compare everything but the digital signature with two binaries too... Not sure
Re:Krypton: phone-based U2F Authenticator by dsr_ on Thursday August 30, 2018 @04:06PM (#17880256)
The overall concept is "reproducible builds". Without it, you have the Reflections on Trusting Trust problem.
Re:Krypton: phone-based U2F Authenticator by gruez on Thursday August 30, 2018 @04:36PM (#17880510)
> With no way to validate that the source code on Github is what ends up in their compiled binaries, I don't see the value to anyone.

you can say the same about all the other open source projects that don't have reproduceable builds.

Re:Krypton: phone-based U2F Authenticator by conradev on Thursday August 30, 2018 @05:55PM (#17881146)
and, in addition, anything you run from the App Store:

https://github.com/signalapp/Signal-iOS/issues/641

Re:Krypton: phone-based U2F Authenticator by jarfil on Friday August 31, 2018 @12:40AM (#17882997)
That's why 90% of Debian packages are reproducible.
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

Re:Krypton: phone-based U2F Authenticator by davefp on Thursday August 30, 2018 @01:59PM (#17879030)
On their FAQ page they state that their app is 'public source'. I assume that is so you (or presumably your organization) can audit (rather than debug) it if necessary.

I've not tried it, but they also suggest you can compile your own binaries from that source to get around the untrusted binary problem.

Re:Krypton: phone-based U2F Authenticator by jwfxpr on Thursday August 30, 2018 @04:49PM (#17880624)
> I've not tried it, but they also suggest you can compile your own binaries from that source to get around the untrusted binary problem.

You could... Except that, if I'm not mistaken, "All Rights Reserved" doesn't allow you to compile and use the code in any way, including diffing.

IINAL, is that an incorrect reading?

Re:Krypton: phone-based U2F Authenticator by pebers on Thursday August 30, 2018 @05:21PM (#17880894)
IANAL either but I agree, that is a statement of copyright which is not unusual, but there is no licence and therefore we have no right to copy & use it.
Re:Krypton: phone-based U2F Authenticator by l2dy on Friday August 31, 2018 @12:05PM (#17886658)
> If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality (for example, through forking).

We are granted a license to use it on GitHub by the GitHub ToS.

https://help.github.com/articles/github-terms-of-service/#5-...

Re:Krypton: phone-based U2F Authenticator by shakna on Thursday August 30, 2018 @09:40PM (#17882294)
> Krypton is public source! You can find it here github.com/kryptco and compile from source [0]

They give permission to compile on the website. Otherwise you would be correct.

[0] https://krypt.co/faq/

Re:Krypton: phone-based U2F Authenticator by gruez on Thursday August 30, 2018 @04:41PM (#17880549)
Re:Krypton: phone-based U2F Authenticator by kbenson on Thursday August 30, 2018 @07:59PM (#17881870)
Theoretically it would be possibly to publish a reproducible compile chain, and as long as required provider secrets are provided separately in the package and read in, and there was a way to checksum individual binaries on Android, that would be an interesting step towards providing assurance of what your phone was running while still allowing them to retain maximum control of the source.

I understand that's a lot of "ifs", but even if it was fully open source, it's hard to use it in anyway that's scale-able, since hardly anyone wants to compile it themselves, and hardly anyone can get it on to their phone by themselves in some ecosystems

It sure would be nice to have some process to ensure my phone was running what I thought it was, even if it required publisher opt-in (and even if it requires I trust the phone OS).

Re:Krypton: phone-based U2F Authenticator by opencl on Thursday August 30, 2018 @03:02PM (#17879699)
This is the business model.

https://krypt.co/devops/pricing/

Re:Krypton: phone-based U2F Authenticator by mplewis on Thursday August 30, 2018 @05:34PM (#17880990)
Correct – their business model is around providing 2FA security for your entire organization.
Re:Krypton: phone-based U2F Authenticator by browsercoin on Thursday August 30, 2018 @05:42PM (#17881052)
who are the end users? organizations that outsources this type of security because it's too difficult to do with existing open source and cloud solutions? What sort of liability insurance do you guys have against data breaches and catastrophic failure?
Re:Krypton: phone-based U2F Authenticator by mplewis on Thursday August 30, 2018 @05:51PM (#17881119)
What sort of open source and cloud solutions give you enterprise 2FA control for tools like GitHub that use SSH authentication?
Re:Krypton: phone-based U2F Authenticator by fao_ on Thursday August 30, 2018 @08:59PM (#17882132)
Incidentally, if they decide to accept pull requests, that "All Rights Reserved" is going to turn it very quickly into a legal Rube Goldberg machine