>> Are you doing these changes on the user's computer or in the cloud?
I'm surprised this wasn't covered in the blog or FAQ. Seems like an important detail that security-minded customers would care about.
22 karma · joined March 18, 2013
I'm surprised this wasn't covered in the blog or FAQ. Seems like an important detail that security-minded customers would care about.
So if you use the same password on any other websites, better change it.
[1] http://arstechnica.com/security/2013/11/how-an-epic-blunder-...
The password leak from last year was really a leak of the password hashes. I'm pretty sure they didn't store passwords in plaintext.
I think the backlash was because they didn't salt the hashes and only used one iteration of SHA1 instead of a more appropriate hash function.
That being said, this doesn't really change the OP's point. Which was, "secure my ass"
Code:
var common_url = '&pagesize=100&order=desc&site=stackoverflow&todate=1363473554';
SO /questions api: todate – Unix timestamp of the maximum creation date on a returned item