4 ms·
There seem like so many ways to make this more secure than a public-but-hard-to-guess URL. Am I missing them? Does anyone have ideas on why it's a bad idea to f
by wcarss 10y ago
There seem like so many ways to make this more secure than a public-but-hard-to-guess URL. Am I missing them? Does anyone have ideas on why it's a bad idea to for example require a login?
Edit: just want to append that this is really neat! I don't think it's dumb at all but my knee-jerk reaction was "aaah somehow this will turn into someone hacking cars that aren't theirs"
- dustball 10y agoI agree users will want something better. I want to learn a little more about who the potential users are before implementing an authentication system for them. For example, if this were to be strictly a consumer app, then Google or Facebook auth would make sense. If this ends up being used by businesses, that speaks to another solution perhaps. Thanks for the feedback!
- OJFord 10y agoCould just start basic - set a passcode on the phone; require it to be entered in the browser.
- mschwaig 10y agoDo you have a problem with this authentication method in general or for this use case? Funnily enough a hard to guess URL can actually be perfectly secure. Google uses them quite a lot inside their services, facebook too I think. https://www.schneier.com/blog/archives/2015/07/googles_unguess.html https://www.schneier.com/blog/archives/2015/07/googles_ungue...