Live data from Hacker News

An Important Message About Yahoo User Security

yahoo.tumblr.com

311–320 of 356 posts

Re: An Important Message About Yahoo User Security

#311
post #65

using 2 Factor Authentication comes handy in situations like this.

Not necessarily. 2FA only prevents access to the account, but passwords are both hard to decrypt and easy to change so I'm not too concerned about that. The real valuable data in this hack are the names, emails addresses, DOBs, telephone numbers, and security questions. Those things are very hard to change and would be very valuable data points for anyone trying to steal your identity or social engineer themselves in…

Yes, you are right. That's really valuable data for anyone impersonating someone. But its becoming more and more difficult which service to use that might protect the information. Hopefully in services like protonmail, everything is encrypted.

Re: An Important Message About Yahoo User Security

#312
post #304
post #293

Earlier quoted context omitted.

Yahoo shouldn't be doing the attribution, it's a conflict of interest[0]. At the moment the standard for incident disclosure is "eventually disclose the leak to users", which some companies, like Yahoo in this case, really stretch. I'd like to see the standard become engaging an outside firm and have them release as much information as possible so that the techniques used, information stolen, potential attribution et…

> Yahoo shouldn't be doing the attribution, it's a conflict of interest What about that would be a conflict of interest? (Just curious)

Their interest is in making the attack look more sophisticated than it may have been, making them look less incompetent because they'd be one of many victims state-backed hacking (they even say that in their statement)

Re: An Important Message About Yahoo User Security

#313
post #205

Earlier quoted context omitted.

Technically, NSA would also be a "state sponsored actor"

So would any corporation receiving government aid, support, favorits, fundings, grants, etc...

Or a some bored kid on welfare

Re: An Important Message About Yahoo User Security

#314

Moving email addresses out from one provider and creating another one is more difficult than moving phone numbers (in the latter case, number portability could help, if available). What exactly can an average/common end user do for such incidents, even if it is to avoid them in the future? I use different passwords across accounts, with all of them being somewhat complex or very complex. I have looked at a few differ…

I create a new email address for every new service I have, with a different password. I literally have 120 different emails that all funnel into the same email address via forwarding.

I tried to do that for a long time. It's nice until you forget exactly what your email is with say, Company X Industries when trying to reset your password. Was it CX@domain.xyz? CXI? CompanyXIndustries? That example is silly but this came up frequently for me. And was super awkward when giving out my email to a CS rep over the phone or "Can you confirm your email address for me?" Me: "something that ends with XP84.cc, I forgot."

Password managers have made this somewhat less painful, at least on the Web, as opposed to "Apps" which refuse to implement the API for using the password -- and username -- stored in your keychain.

Re: An Important Message About Yahoo User Security

#315
post #107

You'd think this would affect the stock price, but currently YHOO only trading down 8 cents (-0.18%). I honestly see this all the time. What sounds like really horrible news for a company, does not affect the price. Howerver, some random analyst or reporter who works at the Mercury Star Sun Inquirer writes a negative article or downgrade and the stock tanks. Doesn't make much sense.

Investors are conflicted: on the one hand, Yahoo had a data breach that will cost them trust, but on the other hand, investors are surprised to hear there are still 500 million Yahoo users.

Yahoo is still the number one or two site in Japan, and with a very old design and logo to boot.

Re: An Important Message About Yahoo User Security

#316
post #242

Earlier quoted context omitted.

Interesting point on the UK laws, but I doubt PII is kept alongside login data, just referenced, and removed as needed without removing a user's login credentials. Far from an expert, but hasn't flagging an account as needing a password change on next login been used as a way to migrate to properly encrypted passwords in the past?

Often. But you want to back it up with a blanket invalidation and password deletion after some grace period, to deal with the case where the user just never logs back in - and a password reset process outside the auth flow, to handle anyone who comes back after that.

A strategy that has worked great for me transitioning off of poorly-thought-out legacy password storage schemes is to take the "bad" hash you have for everyone and treat it exactly as you would a plaintext password - in other words, salt and properly hash it the same way the new passwords are done. Then I delete the unsafe hash and flag that account as "use the old hashing scheme on the password first before normal authentication process, then correctly re-hash and salt the password and store it normally."

Re: An Important Message About Yahoo User Security

#317

You'd think this would affect the stock price, but currently YHOO only trading down 8 cents (-0.18%). I honestly see this all the time. What sounds like really horrible news for a company, does not affect the price. Howerver, some random analyst or reporter who works at the Mercury Star Sun Inquirer writes a negative article or downgrade and the stock tanks. Doesn't make much sense.

Stock price is defined by the expectation of future earnings. If investors have seen in the past that security breaches have no impact on other businesses, why should they react to this ? SONY has had a much worse security breah not too long ago (with stuff stored in plain text!) and people kept using SONY online services anyway.

Re: An Important Message About Yahoo User Security

#318
post #107

Earlier quoted context omitted.

Investors are conflicted: on the one hand, Yahoo had a data breach that will cost them trust, but on the other hand, investors are surprised to hear there are still 500 million Yahoo users.

Yahoo is still the number one or two site in Japan, and with a very old design and logo to boot.

Yahoo in Japan is a different company. It belongs to a different group now, so don't count it in.

Re: An Important Message About Yahoo User Security

#319

Earlier quoted context omitted.

Here is a script for the command line enthusiasts. #!/bin/bash EADDRESS=$([[ "$1" == "" ]] && echo "noreply@example.com" || echo "$1") EADDRESS=$(echo "$EADDRESS" | sed 's;@;%40;') RESPONSE=$( curl "https://heroic.com/wp-admin/admin-ajax.php" \ -H "accept-language: en-US,en;q=0.8" \ -H "accept-encoding: gzip, deflate, br" \ -H "user-agent: Mozilla/5.0 (KHTML, like Gecko) Safari/537.36" \ -H "content-type: application…

EADDRESS=$([[ "$1" == "" ]] && echo "noreply@example.com" || echo "$1") could be replaced with: EADDRESS={$1:-noreply@example.com} From the man page: ${parameter:-word} Use Default Values. If parameter is unset or null, the expansion of word is substituted. Otherwise, the value of parameter is substituted. For: EADDRESS=$(echo "$EADDRESS" | sed 's;@;%40;') you could use: EADDRESS=${EADDRESS/@/%40}

Curious - exactly what man page do you find that in? I've always seen that construction but given that it just uses random punctuation it's impossible to Google it. I don't even know what those are called!!

Re: An Important Message About Yahoo User Security

#320
post #212

Earlier quoted context omitted.

500m users is different than 500m active users, plus I wonder how many people use yahoo for fantasy sports and nothing else

Yahoo hosts the email for many ISPs, including AT&T.

Wait, Yahoo hosts all of AT&T subscribers' email, or there is some cross-account link? Important difference.
Post reply on HN