Wow, they actually posted something about it. Though it was 5 days later when everyone's forgotten about it.
[QUOTE=Keychain;49420428]Wow, they actually posted something about it. Though it was 5 days later when everyone's forgotten about it.[/QUOTE]
Tbh they probably weren't 100% sure what happened. I've never seen anything like that happen let alone on such a huge scale with something like Steam.
According to this, it wasn't even really their fault. There were multiple DoS attacks, and some partner fucked up with their programming.
Look at all the shit that's been swung at Valve, they didn't deserve it. It looks like they're working to get every loose end tied too.
That should give worried people some peace of mind. Glad they are making an effort to contact those affected.
[QUOTE=Higginz511;49420529]Tbh they probably weren't 100% sure what happened. I've never seen anything like that happen let alone on such a huge scale with something like Steam.[/QUOTE]
Definitely looks like they had no idea what was happening since it was someone else's fault.
They, really need more fucking staff just because its an Christmas isn't excuse.
They are a Billion Dollar Company they can afford to pay overtime and have some kind of emergency staff ( or 24/7 whatever )
Everyone will continue to give them shit but honestly Valve did great. They fixed the bug within an hour, sent out preliminary statements the first day, then did their homework and sent out proper statements when the time was right, within the first week.
[QUOTE=theevilldeadII;49420601]they, really need more fucking staff[/QUOTE]
Are you dumb
It happened on early Christmas day, would you really expect there to be a full compliment of staff there?
[QUOTE=Lyokanthrope;49420712]Are you dumb
It happened on early Christmas day, would you really expect there to be a full compliment of staff there?[/QUOTE]
Steam's size and influence [I]DOES[/I] warrant 24/7 personnel monitoring it, and support and PR personnel only a [I]phonecall/text message[/I] and few minutes away for going to work and assess situations.
Guess they don't know their own importance nor the responsibilities that entails.
[QUOTE=RichyZ;49420745]Surely it would have been a better idea to shut down the storefront for a bit while they figured out the issue.[/QUOTE]
um that's what they did
[QUOTE=RichyZ;49420793]They left it up for about an hour.[/QUOTE]
you're assuming that they knew about the issue from the moment it started happening
i'd say 1 hour is a pretty good response time on christmas day
[editline]30th December 2015[/editline]
besides, it was a partner of theirs that fucked up in the first place so they might have not even had anyone at the office
[QUOTE=Van-man;49420747]Steam's size and influence [I]DOES[/I] warrant 24/7 personnel monitoring it, and support and PR personnel only a [I]phonecall/text message[/I] and few minutes away for going to work and assess situations.
Guess they don't know their own importance nor the responsibilities that entails.[/QUOTE]
Why are we pretending that Valve took the day off and didn't fix it within the first couple hours.
[QUOTE=Higginz511;49420905]Why are we pretending that Valve took the day off and didn't fix it within the first couple hours.[/QUOTE]
Because that's too long.
[QUOTE=Lyokanthrope;49420712]Are you dumb
It happened on early Christmas day, would you really expect there to be a full compliment of staff there?[/QUOTE]
This isn't some small mom and pop cafe, this is a major billion dollar company that is not to far be hide Microsoft . They clearly need to expand there system ( more staff, more building for them to work etc. )
[QUOTE=Keychain;49420914]Because that's too long.[/QUOTE]
An hour is far too long for a bug of this size. Think of how many people are concurrently active on Steam within the period of an hour. That's a fucking colossal security risk.
[QUOTE=Keychain;49420428]Wow, they actually posted something about it. Though it was 5 days later when everyone's forgotten about it.[/QUOTE]
I forgot that we lived in the world of CSI where comprehensive investigations are completed within an hour.
[QUOTE=MaddaCheeb;49421002]An hour is far too long for a bug of this size. Think of how many people are concurrently active on Steam within the period of an hour. That's a fucking colossal security risk.[/QUOTE]
0.3% of the userbase was compromised
[QUOTE=Forumaster;49421061]I forgot that we lived in the world of CSI where comprehensive investigations are completed within an hour.[/QUOTE]
I didn't know we lived in a world where literally everything has to settle before you give any form of acknowledgement or reassurance to the people who you may or may not have doxx'd.
[editline]30th December 2015[/editline]
[QUOTE=NixNax123;49421064]0.3% of the userbase was compromised[/QUOTE]
If Steam had 1 million users, which it has far more of than that, that would mean 300,000 people were compromised. Do you realize how small percentages of big numbers is still a lot?
Besides it does't matter if it was literally just one person. That is still way to many and a major fuck on Steam part.
so 3 people think even one person having there information compromised is okay then? okay then
[QUOTE=Keychain;49421084]
If Steam had 1 million users, which it has far more of than that, that would mean 300,000 people were compromised. Do you realize how small percentages of big numbers is still a lot?[/QUOTE]
you mean 3000
[editline]30th December 2015[/editline]
in this case it was 34 thousand people who got minor information leaked. it is not, imo, a "colossal security fuckup".
[QUOTE=Keychain;49420428]Wow, they actually posted something about it. Though it was 5 days later when everyone's forgotten about it.[/QUOTE]
By the looks of things, employees are back since yesterday
Makes perfect sense in the gist if things. A good read though, for some reason I enjoy reading about how these systems work, seeing it as an automated process is great to warn other cdn customers to make sure everything is in check
[QUOTE=NixNax123;49421127]you mean 3000[/QUOTE]
Uhh yeah numbers, something like that.
It's a big deal, just not as big as people thought it was at the beginning.
[QUOTE=NixNax123;49421127]you mean 3000
[editline]30th December 2015[/editline]
in this case it was 34 thousand people who got minor information leaked. it is not, imo, a "colossal security fuckup".[/QUOTE]
34 thousand people who had their addresses and names on account leaked. I'd say that's a pretty big screwup.
I'll be satisfied when they improve there system majorly.
[QUOTE=theevilldeadII;49421254]I'll be satisfied when they improve there system majorly.[/QUOTE]
I'd be satisfied when they'd show they actually [I]CARE [/I]about their users and consumers instead of peddling off official cosmetics in whatever game they feel like paying attention to.
[QUOTE=MaddaCheeb;49421199]34 thousand people who had their addresses and names on account leaked. I'd say that's a pretty big screwup.[/QUOTE]
Iirc not everyone had billing information active in their account page
I remember reading something about if you had bought hardware OR gone over a certain amount in transactions for the year, probably also if your bought something with over card.
This number would have been substantially less, but did happen.
[QUOTE=Van-man;49421352]I'd be satisfied when they'd show they actually [I]CARE [/I]about their users and consumers instead of peddling off official cosmetics in whatever game they feel like paying attention to.[/QUOTE]
That to have they fixed the issue of fixing a compromised steam account ( aka got stolen or something ) in less than 2 weeks. ( aka with in 24 hours )
[QUOTE=MaddaCheeb;49421002]An hour is far too long for a bug of this size. Think of how many people are concurrently active on Steam within the period of an hour. That's a fucking colossal security risk.[/QUOTE]
Think of how many servers and locations get caching info, for the number of people that use Steam during this particular day. It's world-wide. On top of having dickheads DoS'ing them requiring their partners to implement special caching rules to avoid the shit being completely shut down. Finding that error, fixing that error, and then having to get the old information purged from all servers, while getting the new configuration on them. On Christmas day.
An hour is pretty good
Wasn't the fixes implemented after the shutdown, which happened after the hour.
It took an hour to see the issue, have a fucking dedicated valve friend/family moderator get in touch with real valve employee, maybe they had to find someone who understood the Web system, and then hit a killswitch
Getting in contact with valve technicians/developers is not always an easy task, it's possible, but less so on Christmas, wouldn't expect them to be lurking their social media or steam accounts.
The fact that it relied on a forum moderator sees room for critical improvement
Sorry, you need to Log In to post a reply to this thread.