Earlier quoted context omitted.
> Do I need to redo everything from scratch I would hope so. Anything less is not secure. (This is one of the basic "problems" with hardware authentication.) However, the software model allows for pre-arranged cloud sync between multiple devices. Given how Krypton handles PGP/SSH this support isn't there, but there's no technical obstacle.
How are you defining "hardware" here? Plenty of HSMs can export secrets. It's straightforward to have them make a regular export, encrypted such that only the backup HSM can read them. Edit: You simultaneously made a comment saying almost exactly the same thing, so now I really don't understand why you would say anything less than "redo from scratch" is insecure. Is there an unstated assumption of "if you have no oth…
Krypton: phone-based U2F Authenticator
91–100 of 100 posts
Re: Krypton: phone-based U2F Authenticator
#92How does the browser communicate with the phone? Does it require an intermediary server that krypt.co runs?
Yeah, it's using Amazon SQS. It's listed in their docs.
This is horrible. Now the security of it is tied to the security of the stuff they have running in Amazon. Which they probably don't publish source code for? Even if they do, you have no way to know that is what is actually running.
Not the mention reliability and availability concerns.
ah well, I had such high hopes.
Re: Krypton: phone-based U2F Authenticator
#93Can someone explain how this works!? I have looked all over the Krypt website but I still don't get it?!
OK finally found it in the FAQ for those that are slow like me: Is "zero touch" secure? How is it a second factor if it approves automatically? Yes, zero touch is safe. The security behind Krypton is established when you pair Krypton with your browser (via the extension) by scanning the QR code. This ensures that only your specific browser will be able to talk to Krypton. Krypton and your browser establish a secure c…
Re: Krypton: phone-based U2F Authenticator
#94Earlier quoted context omitted.
https://github.com/kryptco/krypton-android/blob/e5e1399caea4... You weren't kidding. :(
Someone paid attention to what Redislabs did, and wanted to get ahead of it. In the most ass way possible.
[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
#95Earlier quoted context omitted.
or you can compile it yourself, or am missing something from you comment?
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.
>Feel free to compile Krypton from source and run it on your phone and workstation. [0]
Re: Krypton: phone-based U2F Authenticator
#96Earlier quoted context omitted.
> 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?
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.
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
#97Earlier quoted context omitted.
Yeah, it's using Amazon SQS. It's listed in their docs.
oy. I'd assumed there was a browser-side USB->BLE plugin. This is horrible. Now the security of it is tied to the security of the stuff they have running in Amazon. Which they probably don't publish source code for? Even if they do, you have no way to know that is what is actually running. Not the mention reliability and availability concerns. ah well, I had such high hopes.
So as long as the source code for both parts (browser-side and phone-side) is there, and you can audit that the code viewable is the code installed, this is pretty solid.
Of course the reliability and availability issue is still there.
Re: Krypton: phone-based U2F Authenticator
#98Re: Krypton: phone-based U2F Authenticator
#99Re: Krypton: phone-based U2F Authenticator
#100So what is the difference between Krypton and Duo? Why are they so innovative? By reading the website it seems they are doing the same thing as Duo.
they are hugely different. Duo is a full SSO and 2FA solution. Krypton supplies a few pieces at the edge.