On Fri, Nov 14, 2008 at 1:20 PM, Jesse Stay <[EMAIL PROTECTED]> wrote: > there's absolutely nothing we can do about it because we have no option > but to store passwords in plain text. >
Store the passwords encrypted then decrypt them when you need to use them. There's a chicken-and-egg problem with where you keep the master key, but if you're clever you can substantially reduce the risk of a breakin exposing passwords. The thing is, OAuth doesn't solve this for you because for any app that would require storing passwords you'll have to persistently store (and protect) various OAuth secrets just the same way you'd need to protect passwords and your master key. As far as using the same password for twitter and your bank account, well, (a) it's a dumb thing to do, and technology cannot protect users from dumbness, and (b) while it helps _you_ the app author avoid risk, OAuth makes users substantially more vulnerable to phishing, so it's kind of a wash in protecting careless users from themselves. -cks -- Christopher St. John http://artofsystems.blogspot.com
