Steam - Allgemeine Diskussion

systems, systems, systems, systems, systems, systems, systems, systems, systems, systems, systems, systems, systems, systems, systems, systems
PSN-Name: Der_Hutmacher

crysmopompas

I am a bot ¯\_(ツ)_/¯
systems, systems, systems, systems, systems, systems, systems, systems, systems, systems, systems
Spielt gerade: GT7 | 60fps FTW
Ich wunderte mich gerade warum Quake Live im Steam Sale ist: Mittlerweile ist das Spiel nicht mehr F2P sondern kostet $10. Premiumabos etc. gibt's nicht mehr.
Alles eigenständige wurde aufgelöst, das Spiel ist nun voll in Steam integriert.
Wer zuvor über Steam spielte behält das Spiel. Wer allerdings bis zuletzt über den eigenen Client spielte muss das Spiel nun kaufen.
 
systems, systems, systems, systems, systems, systems, systems, systems, systems, systems, systems, systems
PSN-Name: maxmontezuma
Spielt gerade: Hogwarts Legacy
Jo, PayPal / Kreditkarten / Adressen alles sichtbar wenn man durch "Glück" auf einen entsprechenden Account landet.

---------- Beitrag um 22:20 Uhr hinzugefügt ---------- Vorheriger Beitrag um 22:19 Uhr ----------

It goes without saying, but avoid logging into any Steam websites until the issue has been remedied.

If you know you're already logged in, do NOT visit any Steam Community or Steam Store URL.
This includes any internet browser and the Steam Desktop/Mobile Client!
Playing games online should be fine. It'll prevent anybody else from logging into your account via desktop client.

Explanation according to Steam DB:

Valve is having caching issues, allowing users to view things such as account information of other users.
Aber das wird sicher wieder gut heruntergespielt und unter den Teppich gekehrt - aber wehe man kann mal 2 Stunden nicht im PSN oder Xbox Live Online zocken ;)
 
systems, systems, systems, systems, systems, systems, systems, systems, systems, systems, systems, systems
PSN-Name: maxmontezuma
Spielt gerade: Hogwarts Legacy
Falls PayPal mit dem Account verbunden ist, dann sollte man es lieber über die PayPal-Seite "abkoppeln":

[ame]https://twitter.com/itsexe/status/680490931141914625[/ame]

Hab schon Screenshots gesehen, wo Leute zum trollen über fremde Accounts dann für mehrere hundert Dollar Spiele gekauft haben ~lol~

---------- Beitrag um 23:00 Uhr hinzugefügt ---------- Vorheriger Beitrag um 22:56 Uhr ----------

[ame]https://twitter.com/SneezingPrince/status/680505507275210752[/ame]

~lol~ ~lol~ ~lol~
 
systems, systems, systems, systems, systems, systems, systems, systems, systems, systems, systems, systems, systems
PSN-Name: Dojii
Da haben sich wohl die Hacker Kiddies verklickt und statt, wie angekündigt, PSN und XBox Live leider Steam erwischt.

Kann ja mal passieren. Sind ja auch nur 14jährige Menschen, die bei Mutti wohnen.
 

crysmopompas

I am a bot ¯\_(ツ)_/¯
systems, systems, systems, systems, systems, systems, systems, systems, systems, systems, systems
Spielt gerade: GT7 | 60fps FTW
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.
http://kotaku.com/steam-goes-nuts-offers-access-to-other-peoples-account-1749718979
 
systems, systems, systems, systems, systems, systems, systems, systems, systems, systems, systems, systems
PSN-Name: maxmontezuma
Spielt gerade: Hogwarts Legacy
We'd like to follow up with more information regarding Steam's troubled Christmas.

What happened

On December 25th, a configuration error resulted in some users seeing Steam Store pages generated for other users. Between 11:50 PST and 13:20 PST store page requests for about 34k users, which contained sensitive personal information, may have been returned and seen by other users.

The content of these requests varied by page, but some pages included a Steam user’s billing address, the last four digits of their Steam Guard phone number, their purchase history, the last two digits of their credit card number, and/or their email address. These cached requests did not include full credit card numbers, user passwords, or enough data to allow logging in as or completing a transaction as another user.

If you did not browse a Steam Store page with your personal information (such as your account page or a checkout page) in this time frame, that information could not have been shown to another user.

Valve is currently working with our web caching partner to identify users whose information was served to other users, and will be contacting those affected once they have been identified. As no unauthorized actions were allowed on accounts beyond the viewing of cached page information, no additional action is required by users.

How it happened

Early Christmas morning (Pacific Standard Time), the Steam Store was the target of a DoS attack which prevented the serving of store pages to users. Attacks against the Steam Store, and Steam in general, are a regular occurrence that Valve handles both directly and with the help of partner companies, and typically do not impact Steam users. During the Christmas attack, traffic to the Steam store increased 2000% over the average traffic during the Steam Sale.

In response to this specific attack, caching rules managed by a Steam web caching partner were deployed in order to both minimize the impact on Steam Store servers and continue to route legitimate user traffic. During the second wave of this attack, a second caching configuration was deployed that incorrectly cached web traffic for authenticated users. This configuration error resulted in some users seeing Steam Store responses which were generated for other users. Incorrect Store responses varied from users seeing the front page of the Store displayed in the wrong language, to seeing the account page of another user.

Once this error was identified, the Steam Store was shut down and a new caching configuration was deployed. The Steam Store remained down until we had reviewed all caching configurations, and we received confirmation that the latest configurations had been deployed to all partner servers and that all cached data on edge servers had been purged.

We will continue to work with our web caching partner to identify affected users and to improve the process used to set caching rules going forward. We apologize to everyone whose personal information was exposed by this error, and for interruption of Steam Store service.
Naja.
 
Top