Timeline for Decrypt Passwords based on using a user's password
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 9, 2014 at 4:19 | answer | added | David | timeline score: 1 | |
| Apr 23, 2014 at 18:36 | comment | added | mikeazo | This one just came up that is related: security.stackexchange.com/questions/56477/… | |
| Apr 17, 2014 at 8:28 | history | tweeted | twitter.com/#!/StackSecurity/status/456710748853391360 | ||
| S Apr 15, 2014 at 20:52 | history | suggested | KnightOfNi | CC BY-SA 3.0 |
fixed grammar and sentence structure
|
| Apr 15, 2014 at 20:52 | review | Suggested edits | |||
| S Apr 15, 2014 at 20:52 | |||||
| Apr 15, 2014 at 19:50 | comment | added | traisjames | @mikeazo I thought about that while looking at related results while writing the OP. Two of our other websites, GedMatch.com and Ancestry.com do not support OAuth or anything besides Ancestry supporting Facebook connection. | |
| Apr 15, 2014 at 19:34 | comment | added | mikeazo | The best way would be to use a more secure delegation system (like OAuth). That way your customer's don't have to give you their credentials. It looks like 23andme supports OAuth (api.23andme.com/docs). Not sure if the other services you would need to access do, however. | |
| Apr 15, 2014 at 19:25 | history | migrated | from crypto.stackexchange.com (revisions) | ||
| Apr 15, 2014 at 19:23 | comment | added | traisjames | That is correct. They don't need to see the key themselves, just have the key stored in the program to convert the password to clear text. | |
| Apr 15, 2014 at 19:15 | comment | added | mikeazo | Let me see if I get this straight. The employee enters their password which gives them the key to encrypt/decrypt the customer's password. All employees will likely have different passwords though, correct? | |
| Apr 15, 2014 at 18:19 | history | asked | traisjames | CC BY-SA 3.0 |