News for hackers. Stuff that matters.
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.