4 ms·
This is a little off-topic but I would still like someone from ifttt to answer in more detail the method that they use to store passwords for 3rd party sites.
by newman314 14y ago
This is a little off-topic but I would still like someone from ifttt to answer in more detail the method that they use to store passwords for 3rd party sites.
I think this is an important detail for an app like ifttt as they necessarily have to store the actual passwords in a form that they can reverse encryption (for websites that do not support something like OAuth) for in order to submit on the user's behalf. So it's important to get some transparency on the mechanism by which ifttt does this.
I also posed the question here a while ago:
http://www.quora.com/How-does-ifttt-securely-store-passwords-for-sites-that-do-not-use-OAuth-or-similar-methods http://www.quora.com/How-does-ifttt-securely-store-passwords...
- JoshTriplett 14y ago> I also posed the question here a while ago: http://www.quora.com/How-does-ifttt-securely-store-passwords-for-sites-that-do-not-use-OAuth-or-similar-methods http://www.quora.com/How-does-ifttt-securely-store-passwords... And you appear to have received an answer there, as well. Anything using OAuth doesn't need to store passwords, and for anything else ifttt stores the password in an encrypted (but obviously retrievable) form. I don't see how they could do otherwise; at most, they could refuse to interoperate with any sites not supporting OAuth, and I don't see the benefit to that.
- newman314 14y agoTo be clear, I was looking for more detail around how they were doing the reversible encryption.