l_l shares
17 years ago
That Plurk sends unencrypted usernames and passwords through POST requests. Isn't that insecure?
latest #15
BenFeldman asks
17 years ago
if anything is *truly* secure.
l_l
17 years ago
Well, isn't that less secure?
BenFeldman says
17 years ago
it is less secure... does Twitter do the same?
立即下載
Chris
17 years ago
Most sites do that.
l_l
17 years ago
Wow...I didn't realize they both did that. Learn something new every day.
riverjiang says
17 years ago
that it's a huge pain in the butt to set up https, which is why most webapps don't bother encrypting passwords outside of the db.
l_l
17 years ago
I'm not necessarily saying HTTPS, but could they at least hash the passwords or something? I know little of developing web sites.
riverjiang
17 years ago
Hm, that's a good idea—hashing it before sending the data. The people who don't have JS enabled wouldn't be secure, though.
l_l
17 years ago
But they wouldn't be able to view the site either, no?
Chris
17 years ago
Then the hashkey would be public, so it doesn't exactly help.
riverjiang
17 years ago
well, no—you could just use a SHA1 hash, and match it up with the one from the database.
riverjiang
17 years ago
With the people who have javascript disabled, you could do what you did before—hash the supplied password, then match it up with the db's.
Chris
17 years ago
True.
l_l
17 years ago
Man, I am completely lost.
back to top