Guys... let's just delete our Yahoo accounts. That company can't go bankrupt fast enough. It will sell our data for quarters.
Yahoo discloses hack of 1B accounts
71–80 of 596 posts
Re: Yahoo discloses hack of 1B accounts
#72MD5 in 2016?.I hope yahoo can save itself and tech community all this embarrassment by just going out of business one and for all.Folks at the helm of affairs at yahoo are incompetent. And it is about time government started to persecute incompetent CEO.
Re: Yahoo discloses hack of 1B accounts
#73Re: Yahoo discloses hack of 1B accounts
#74Guys... let's just delete our Yahoo accounts. That company can't go bankrupt fast enough. It will sell our data for quarters.
Is it possible to extract all emails+contacts from yahoo without paying ? furthermore my paypal account is linked to yahoo.
Re: Yahoo discloses hack of 1B accounts
#75Earlier quoted context omitted.
Bloody hell. Sloppy and incompetent.
I'm genuinely curious how the decision to use MD5 gets made. Who says, "hey, maybe we should use MD5." And then who responds, "that sounds like a great idea Bob." Seriously. I've known for years that MD5 is insufficient for hashing passwords and I'm just some random guy. This kind of thing really baffles me.
I'm not really a software developer but I really can't imagine it being a huge change. Instead of md5(pass) you could probably just change that to secure_hash(md5(pass), salt), add another column in the database for the salt, and rehash all the passwords. Customers wouldn't notice. Rehashing the databases would take a while, but otherwise that's really not a huge amount of work.
Re: Yahoo discloses hack of 1B accounts
#76Guys... let's just delete our Yahoo accounts. That company can't go bankrupt fast enough. It will sell our data for quarters.
But that's where all my junk mail goes...
Re: Yahoo discloses hack of 1B accounts
#77Earlier quoted context omitted.
Web tokens, for example, don't necessarily include just a session ID. Some include the full session details within its payload. This can be quite useful, actually, because it offloads session-lookup onto the client.
How do you invalidate a JWT server-side without the user interacting with the server ?
Re: Yahoo discloses hack of 1B accounts
#78Earlier quoted context omitted.
Web tokens, for example, don't necessarily include just a session ID. Some include the full session details within its payload. This can be quite useful, actually, because it offloads session-lookup onto the client.
How do you invalidate a JWT server-side without the user interacting with the server ?
Re: Yahoo discloses hack of 1B accounts
#79"Separately, we previously disclosed that our outside forensic experts were investigating the creation of forged cookies that could allow an intruder to access users’ accounts without a password. Based on the ongoing investigation, we believe an unauthorized third party accessed our proprietary code to learn how to forge cookies." So that exactly explains how my Yahoo account was used to send spam despite having a pa…
EDIT: To clarify, I mean specifically with md5. I'm by no means an expert, just curious because I had considered md5 so broken that this comment caught my attention.