Has valve issued a new statement?
No, they are still eating Zanzibars.
Has valve issued a new statement?
prior preparation prevents piss-poor performance
it's not beyond their scope to plan and test for this and make sure that infrastructure can support worst-case scenarios
making a config change at this date/time and with this much impact was amateur hour
Well, the way it was handled was poor, no doubt, considering the result. But that you make changes when the load hits, not so sure that's amateurish, but those who have worked with similiar systems might be able to fill in with more details. My own practical experience are with systems with much smaller usersbases.
Going to be using Steam much less after that response. Which won't be hard considering the prices they charge outside of sales.
There are so many warning signs around how Valve are run. They need more dedicated staff regardless of culture. This should not just happen.
There are a lot of things that shouldn't happen, but the reality is that most services have major security leaks. Neogaf had a major leak last week that required a lot of people to change their password.
In the last couple of years alone; http://www.informationisbeautiful.net/visualizations/worlds-biggest-data-breaches-hacks/
Nobody can rely on any site to keep your information safe from attacks. It's not how it should be, but it's how it is.
http://kotaku.com/steam-goes-nuts-offers-access-to-other-peoples-account-1749718979Where's Valves response?
Steam is back up and running without any known issues. As a result of a configuration change earlier today, a caching issue allowed some users to randomly see pages generated for other users for a period of less than an hour. This issue has since been resolved. We believe no unauthorized actions were allowed on accounts beyond the viewing of cached page information and no additional action is required by users.
There are a lot of things that shouldn't happen, but the reality is that most services have major security leaks. Neogaf had a major leak last week that required a lot of people to change their password.
In the last couple of years alone; http://www.informationisbeautiful.net/visualizations/worlds-biggest-data-breaches-hacks/
Nobody can rely on any site to keep your information safe from attacks. It's not how it should be, but it's how it is.
So because Facebook is free we shouldn't care when they leak your private communications? Ridiculous argument.Shit can happen, expecially if hackers are involved. But Neogaf doesn't store your CC or private info anyway, it's a free service so no one should argue if something bad happens, expecially if it's no one's fault.
In what situation would you not start the time calculation at the first reported occurrence of the issue?
I'll speak on behalf of SteamDB here. We always tweet and post information on our blog only after verifying it ourselves, we didn't base our information on speculation, but rather on our own research. It was pretty clear that it was a caching issue, as it was caching the first non-cache hit on any url (you could easily test this by adding ?something=random to the url, and then loading it from another browser/machine while not being logged in).
I believe this was caused by a misconfiguration on Akamai (Valve's CDN), which caused this to happen. You can use Akamai's debug headers to get some interesting information, and during the issue it was showing X-Check-Cacheable: YES at all times, which is not good. There are no indications that anything could be done on your behalf (caching is read-only).
Yes, we know we know we shouldn't be speaking for Valve, but we find it more important to keep users aware of the issue. Our track record is pretty damn good in that sense, and if the response Gamespot/Kotaku received from Valve is indeed correct, we pretty much nailed our caching theory.
Before publishing the blog post, we had multiple people that work closely on Steam (besides us) proof read it too.
I always thought Valve would be like Amazon and have a fairly good security history. After all the Sony hacks though I stopped storing my debit card and address anywhere. Feeling pretty justified about that now. 20 seconds inconvenience every time I check out vs. having some hackers have my personal info.
So because Facebook is free we shouldn't care when they leak your private communications? Ridiculous argument.
If I make a statement about an issue I caused I usually start the timing when the information reaches me to the point where the fix has been shipped. When splitting hairs like 30 minutes it's always important to remember that rolling out things takes time and thats how it is. Would the statement made you feel safer if it laid out things by the minute? Maybe.
It's not that it's 30 minutes or splitting hairs. It's that for a good 2 and something hours, there's radio silence on Steam's end for such a widespread problem.
If you leave people in the dark for a long time, without a word or otherwise, during a time period where you can randomly view other people's information, it behooves you to drum up something.
There's nothing wrong with the time period it takes to fix the problem. You gotta do what you gotta do, regardless of how bad the fuck up is. But there's no way Valve didn't see that shit for hours.
I'll speak on behalf of SteamDB here. We always tweet and post information on our blog only after verifying it ourselves, we didn't base our information on speculation, but rather on our own research. It was pretty clear that it was a caching issue, as it was caching the first non-cache hit on any url (you could easily test this by adding ?something=random to the url, and then loading it from another browser/machine while not being logged in).
I believe this was caused by a misconfiguration on Akamai (Valve's CDN), which caused this to happen. You can use Akamai's debug headers to get some interesting information, and during the issue it was showing X-Check-Cacheable: YES at all times, which is not good. There are no indications that anything could be done on your behalf (caching is read-only).
Yes, we know we know we shouldn't be speaking for Valve, but we find it more important to keep users aware of the issue. Our track record is pretty damn good in that sense, and if the response Gamespot/Kotaku received from Valve is indeed correct, we pretty much nailed our caching theory.
Before publishing the blog post, we had multiple people that work closely on Steam (besides us) proof read it too.
It's got nothing to do with stress testing, if the caching issue occurred at all it would've presented with 5 users let alone 5 million. They didn't do their due diligence and in the process user data was leaked.
Steam was down for "routine maintenance" for me for a while around that time. Or so my friends list on the client told me. After I read the thread I assumed they had turned some things off until it was fixed. I'd say probably an hour if not more.Can someone help me clear some confusion: did or did not Valve shut down Steam at any point? If yes, for how much time? I'm trying to pinpoint when exactly the problem began and when it ended.
Ludens there are people on this website who leak insider information in an anonymous capacity. Some of them are vetted by moderators. If that information were to get out into the public domain then people could potentially lose their jobs. I don't know perhaps people are vetted with off site e.mails but to me that seems reason enough to have responsible security measures.
Your whole concept of paid vs. free services remains flawed in my opinion. Security should be based on what there is to be lost. That can be information, reputational damage, all sorts of things that goes beyond what fields or financial relationships the organisation and users have.
Can someone help me clear some confusion: did or did not Valve shut down Steam at any point? If yes, for how much time? I'm trying to pinpoint when exactly the problem began and when it ended. I'm reading on some info sites that Valve did shut down Steam, and I'm pretty sure people here said that Valve never shut down Steam. I'm wary of misinformation.
This was not an attack. And its more the response. They caused it and reacted both slowly and flippantly.
What is really shitty is their statement: they didn't apologize, they took this like nothing. This is infuriating and disrispectful toward their customers, plain and simple.
Steam was down for "routine maintenance" for me for a while around that time. Or so my friends list on the client told me. After I read the thread I assumed they had turned some things off until it was fixed. I'd say probably an hour if not more.
I think community side was up the whole time. They shutdown the store though. Based on a post I made the store came back up around 1 am (gmt+2). Don't know what functionality was available at that time but I was able to access the store.
No, it's called honesty. If you claim an issue was live for "less than an hour" when there's public evidence from others affected by the issue well before that time, I'm going to call bullshit on your claim.If I make a statement about an issue I caused I usually start the timing when the information reaches me to the point where the fix has been shipped. When splitting hairs like 30 minutes it's always important to remember that rolling out things takes time and thats how it is. Would the statement made you feel safer if it laid out things by the minute? Maybe.
Strange. Delinking from Steam shouldn't affect Paypal, you're just removing the info on Steam's end but as far as Paypal knows it still has an open account with them and will approve any transfer automatically
Check this screen for https://www.paypal.com/cgi-bin/webscr?cmd=_manage-paylist for WWW.Steampowered.com with status of Active
I'm okay with them not apologising. I care more about it not happening again. I wonder if they have good reasons for not doing it.
Also, I would never take a company apology at face value. That's just PR speak. I find most apologetic releases to be insincere and really have a brush off rhetoric. I'd rather people hold them up on it instead of being outraged over a lack of a PR release (which doesn't mean much).
I think putting your phone number for 2 way verification and/or for emergency recovery is worth it.. worst scenario you deal with some prank. But you have extra method to recover your account.I have got into my account, everything seems ok, I had no payment info on my account anyway, I don't have my phone number in there either, would it be advisable for me to put my phone number in for verification reasons? I don't use my PC/Steam for games very much so I don't know if it's worth it, but then again if something like this does happen again I don't want to lose access to my Steam account.
Advice/thoughts/views please.
So is it 100% safe now to login and purchase stuff?
I hope so because I've logged in and purchased stuff >_>So is it 100% safe now to login and purchase stuff?
I'll speak on behalf of SteamDB here. We always tweet and post information on our blog only after verifying it ourselves, we didn't base our information on speculation, but rather on our own research. It was pretty clear that it was a caching issue, as it was caching the first non-cache hit on any url (you could easily test this by adding ?something=random to the url, and then loading it from another browser/machine while not being logged in).
I believe this was caused by a misconfiguration on Akamai (Valve's CDN), which caused this to happen. You can use Akamai's debug headers to get some interesting information, and during the issue it was showing X-Check-Cacheable: YES at all times, which is not good. There are no indications that anything could be done on your behalf (caching is read-only).
Yes, we know we know we shouldn't be speaking for Valve, but we find it more important to keep users aware of the issue. Our track record is pretty damn good in that sense, and if the response Gamespot/Kotaku received from Valve is indeed correct, we pretty much nailed our caching theory.
Before publishing the blog post, we had multiple people that work closely on Steam (besides us) proof read it too.
Thank you for sharing this, and I want to tell you that you did a great job at communicating to the users where Valve did not during this.
Is there any way of telling who was affected based on your knowledge about the caching system? I have my doubts that Valve will come forward at this point with any further information so customers can safely rest knowing they were not affected or take necessary security measures if they were.
As far as anyone not working at valve would know, yes. I say go for it.So is it 100% safe now to login and purchase stuff?
Had this been Sony or Microsoft, people would have gone batshit insane, right now.
I guess I will have to buy prepaid cards for Steam just like I do for other services from now on.
Yeah, one of the bigger things that bothers me is the lack of care that went into the explanations. You owe it to your consumer to be honest and upfront about the problems and issues to better arm themselves.
If I read that statement, I'd have never known my personal information and last digits of my card were open to anyone in the damn world. That's completely inexcusable.