kevjiang | 11 years ago | on: Automated password changing
kevjiang's comments
kevjiang | 11 years ago | on: Was jquery.com compromised?
kevjiang | 12 years ago | on: Hijacking user sessions with the Heartbleed vulnerability
kevjiang | 12 years ago | on: Can Snowden be targeted using the Adobe breach?
So if you use the same password on any other websites, better change it.
kevjiang | 12 years ago | on: Can Snowden be targeted using the Adobe breach?
[1] http://arstechnica.com/security/2013/11/how-an-epic-blunder-...
kevjiang | 12 years ago | on: Did these guys just reinvent the Web?
kevjiang | 12 years ago | on: It's A Terrible Time To Buy An Expensive House
kevjiang | 12 years ago | on: Why I Just Closed My LinkedIn Account
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"
kevjiang | 13 years ago | on: Must-have OS X apps for developers and designers
kevjiang | 13 years ago | on: Show HN: XKCD-inspired StackSort
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
I'm surprised this wasn't covered in the blog or FAQ. Seems like an important detail that security-minded customers would care about.