News for hackers. Stuff that matters.
Re:Password Breach? That'll Be $172,000,000 Please by brennenHN on Friday January 25, 2013 @02:37PM (#5117215)
This is why we're storing important user credentials on a user's phone instead of all on a central server! (https://clef.io)
Re:Password Breach? That'll Be $172,000,000 Please by ScottWhigham on Friday January 25, 2013 @03:02PM (#5117327)
Is this just thinly veiled spam for that site? I can't tell if you work for them or not but, if you do, it's not in your profile. If so, I think it's pretty tacky when companies to take every possible opportunity to get their name out there...
Re:Password Breach? That'll Be $172,000,000 Please by chunsaker on Friday January 25, 2013 @03:17PM (#5117381)
Profile updated. Thanks, didn't mean to be disingenuous. Its okay to call me tacky - I actually think this stuff matters.
Re:Password Breach? That'll Be $172,000,000 Please by scrumper on Friday January 25, 2013 @04:11PM (#5117655)
I think ScottWhigham was talking about brennanHN rather than you. Nothing tacky about your submission.
Re:Password Breach? That'll Be $172,000,000 Please by jlkinsel on Friday January 25, 2013 @03:01PM (#5117321)
Hmm...that seems to have potential, but it requires custom integration and users to use your app.

Is there an open protocol for this?

Looks like you're doing something similar to the mutual auth that wikid does...a whitepaper or two with more depth would be useful on the site

Re:Password Breach? That'll Be $172,000,000 Please by anExcitedBeast on Friday January 25, 2013 @04:50PM (#5117876)
This is pointless. Solutions like keepass are just as good and don't require existing services to hook into new authentication API's. In fact, they're better because they don't run the risk of opening a whole new central attack surface.
Re:Password Breach? That'll Be $172,000,000 Please by chunsaker on Friday January 25, 2013 @02:39PM (#5117222)
What happens if your phone gets stolen?
Re:Password Breach? That'll Be $172,000,000 Please by dasil003 on Friday January 25, 2013 @02:58PM (#5117312)
0.0000014286% of the damage that happens when Sony's database gets hacked (assuming equal payload).
Re:Password Breach? That'll Be $172,000,000 Please by dmix on Friday January 25, 2013 @04:31PM (#5117769)
As a consumer though, I could change my password on a server if it gets stolen. But how would I reset it after my phone was stolen if authentication is all stored client side?
Re:Password Breach? That'll Be $172,000,000 Please by mistercow on Friday January 25, 2013 @02:53PM (#5117289)
Then one user's password gets stolen, as opposed to thousands.
Re:Password Breach? That'll Be $172,000,000 Please by chunsaker on Friday January 25, 2013 @03:08PM (#5117351)
Yes, it certainly mitigates the scale of a potential breach and I like that the reduced scale/potential value makes it a less attractive target to hackers (assuming the server side is also built in a secure way). I havent investigated, but it makes me nervous to think that if my phone is stolen, the thief gets my data too.
Re:Password Breach? That'll Be $172,000,000 Please by freehunter on Friday January 25, 2013 @03:39PM (#5117504)
Use a PIN, and if possible, encrypt your phone. It won't completely mitigate the risk, but it will reduce your surface area.
Re:Password Breach? That'll Be $172,000,000 Please by kdude63 on Friday January 25, 2013 @02:42PM (#5117238)
Then wouldn't that be the user's fault/problem?
Re:Password Breach? That'll Be $172,000,000 Please by chunsaker on Friday January 25, 2013 @02:46PM (#5117258)
Sure, but designing around the inherent riskiness of user behavior/forgetfulness is an important part of security systems. Users want to be protected, not for blame to be shifted to them.