Re:Web Authentication: Proposed API for accessing Public Key...
by jessaustin on Tuesday April 10, 2018 @12:18PM
(#16802498)
If, as GP suggests, you have to plug a USB device in to auth the first time, why not just run the protocol through the device for every single HTTP request? Then, if the user unplugged the device, future requests would fail, right? I don't know if the protocol under discussion forbids that, but it seems like an easy change?
[ Parent
| on HN ]
Re:Web Authentication: Proposed API for accessing Public Key...
by djrogers on Tuesday April 10, 2018 @01:34PM
(#16803248)
A USB device would only be one of many options - relying on it would be pretty backward looking.
Re:Web Authentication: Proposed API for accessing Public Key...
by jessaustin on Tuesday April 10, 2018 @03:46PM
(#16804575)
Other things would have other options. You might have a bluetooth or nfc device that has a "momentary" button, that e.g. you have to press less than five seconds before any particular web request.
Re:Web Authentication: Proposed API for accessing Public Key...
by filleduchaos on Tuesday April 10, 2018 @05:53PM
(#16805878)
That's a straight path to frustration on today's web
Re:Web Authentication: Proposed API for accessing Public Key...
by vokep on Tuesday April 10, 2018 @07:16PM
(#16806528)
maybe, a better solution might be just doing a serverside 'authenticity ping' every x seconds, and if that fails then you get kicked out.
This would leave a window of x seconds after logging out in which attacks could occur but that could be mitigated by requiring a failed request on logout (perhaps require the usb key to be removed upon logout, send an auth-ping, and only give a successful logout message if the auth-ping fails. (Even without this mitigation I'm not sure what kind of attack would work for the inbetween X seconds, but might as well mitigate it in case someone else could think of something)