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.
> 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.
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.