Chrome Key: Building a Hardware Authentication Device Emulator • Hacker News Board

Re: Chrome Key: Building a Hardware Authentication Device Emulator

#11

Post by joaomppeixoto » Wed, Feb 20, 2019, 2:44 AM UTC

amelius wrote: post #4

Nice but I'm on Firefox.

LIke techsupporter mentioned, this post series is more of a run through. I'm open sourcing the whole project and intend to add support to other browsers. Since it uses standard apis it should just work TM.

There are some parts copied from krypt.co with their permission, and I did see their multi browser support, which will help with that.

Re: Chrome Key: Building a Hardware Authentication Device Emulator

#12

Post by jiveturkey » Wed, Feb 20, 2019, 5:05 PM UTC

jiveturkey wrote: post #2

totally silly. they also implemented the test of user presence (TUP). there's little point to a software version of a U2F token if user-interaction is still required.

downvotes with no comments. sigh.

Re: Chrome Key: Building a Hardware Authentication Device Emulator

#13

Post by nacs » Thu, Feb 21, 2019, 2:42 PM UTC

IX-103 wrote: post #8

tambourine_man wrote: post #3

As an aside, that is one cool about page: https://blog.joaopeixoto.net/about/

But using more than 100% of his memory kind of takes away from it. I guess those defunct processes could be swapped to disk, but who keeps more than twice their RAM in swap space...

I'm guessing the CPU % column is for showing how hard he worked at each job..

Re: Chrome Key: Building a Hardware Authentication Device Emulator

#14

Post by nacs » Thu, Feb 21, 2019, 2:48 PM UTC

Love the writeup.

I like how you walk through the concepts and show code snippets instead of just writing a "here's what I did" in a paragraph then linking a Github repo. Great little introduction to web extensions and webauth too.