10 ms·
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? The
by jessaustin 9y ago
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?
- djrogers 9y agoA USB device would only be one of many options - relying on it would be pretty backward looking.
- jessaustin 9y agoOther 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.
- filleduchaos 9y agoThat's a straight path to frustration on today's web
- deleted 9y ago[deleted]
- rapind 9y agoMight as well just boot linux from a USB at that point.
- ithkuil 9y agosadly just being able to boot your OS is not enough to trust the resulting hardware+OS combo
- vokep 9y agomaybe, 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)