GitHub supports Universal 2nd Factor authentication

Post by Rafert » Sat, Oct 03, 2015, 11:07 AM UTC

moreati wrote: post #66

A few U2F details worth mentioning Browser support is currently limited to Chrome, and possible Windows Edge* For now it only works with USB. Bluetooth and NFC specs are out, browser support is the bottleneck The protocol is public/private key based, with the private key strongly encouraged to be in tamper resistant/evident storage. The protocol is authentication method agnostic. It doesn't care if you use a USB key,…

Post by Rafert » Tue, Oct 06, 2015, 5:11 PM UTC

moreati wrote: post #82

Rafert wrote: post #81

Earlier quoted context omitted.

Thanks for the link to your presentation. I'm currently implementing this in a Rails app and had a bit of a hard time to grok U2F with only the info from Fido site. Your talk will make it easier for my colleagues to understand U2F :)

Have you seen https://github.com/castle/ruby-u2f ? As linked from https://developers.yubico.com/U2F/Libraries/List_of_librarie...

Post by co0nsta » Wed, Oct 07, 2015, 1:09 PM UTC

co0nsta wrote: post #84

philip1209 wrote: post #15

I like this because I keep a U2F Neo-n device permanently in my laptop USB port. It's just more convenient for services that support it. In the future, I would like to require it for employees on our app. However, when I go into Github to turn it on (in chrome using U2F devices I have already used with Google) it says "This device cannot be registered." Even when I remove the device it says that. I'm disappointed tha…

I had this problem too, and it turned out my system wasn't configured correctly. I had to download https://github.com/Yubico/libu2f-host/blob/master/70-u2f.rul... to /etc/udev/rules.d and then udevadm control --reload-rules . Worked fine after that. HTH.