安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题
Request a refund or possibly play only in offline node and wait.
You got the clause that says security vulnerabilities can apply?
Why?
Because you will have given reasonable time for the dev to acknowledge and address the issue with a patch.
Notice how the thread does not identify the newly registered CVE, so it's not a "new" issue at all.
...Hmm, they have just taken their servers offline as a precaution, turns out the good guys do care.
Yup, the thing is technically such an action happening immediately invokes the part of the EU legislation, but on the other hand it means they must have adequate time to try and fix it.
So in any case, a refund they can simply say "nah, we';re ficing it mate".
Elden Ring is around the corner and will likely re-use some of the netcode, that is present in previous souls-games. Plus with all the recently generated buzz from the Dark Souls community, it is no wonder, why they're doing something now. While there was and still is more fear-mongering than a healthy dose of caution (though it might have actually helped kick things into motion this time), ignoring the exploit thus far was definitely not helping either and just helped escalating things.
Stick to the subject.
People are lucky it's even being supported since the release shows 2016 for DS3, which is far outside of an expected EOL or reasonable scenario of allowing a refund or expectations of support, which is part of any competent law or defensive abilities to disallow abuse of any particular law. If the game runs/plays well, that's that; an exploit in something is hardly a reason to allow refunds, since an OS is constantly exploited and often is why 3rd party software is introduced to protect against ever-evolving issues, yet you can't just refund an OS purchase any day/year you want.
This is about the games functionality. As for the subject of this thread; clearly they're resolving the issue, especially since usually companies becoming alerted of such love to patch out such exploits to keep their customer base happy.
True, but the situation is different, if a company knows about an exploit but does not do anything about it until it escalates or if they don't even warn their customers, so they could add security measures of their own.
Thankfully, they're patching it anyway, so people don't have to worry about this if they update the game.
A streamer of some repute had the actual RCE exploited live on a Twitch Stream, for everyone to see. That basically forced Bamco's hand.
They're not doing this because they're 'the good guys' - or they would've done this long, long ago with all the other RCE-vulnerabilities in not just Dark Souls 3, but also Dark Souls and Dark Souls 2. (And allegedly Elden Ring as well, when it would have released - considering the fact that the netcode between these games has changed very, very little over time and is mostly a copy&paste.)
The reason they now took all of it offline is because it's all vulnerable and this has been public knowledge for, what? - a decade? Longer? It was basically a ticking time-bomb.
Sure. See below, emphasis mine.
You may very well expect for a triple-A video game not to contain a readily exploitable RCE-vulnerability.
The 'EU stuff' does in fact matter; and yes, a lot of expensive software could end up in non-conformity at which point (EU-)consumers could exercise their right to a remedy for said lack of conformity, meaning they could demand that the seller have the product fixed - and if they seller refuses, they could demand a partial refund proportional to the loss of functionality and retain the product; or terminate the contract and lose access to the product.
But they haven't yet because national legislation based on this directive is new and only entered into force start of this month. Moreover; if push comes to shove, it would require taking the seller to court and that's quite a leap in costs to make for what would otherwise just be a € 50 - € 70 loss.
You'd have to have the luck -- or bad luck; matter of perspective -- that someone with deep pockets and a strong sense of morality ends up affected by such a problem and is willing to make a case out of it on principle.
Except in case of the EU, they disagree with you on that point:
Digital distribution via Steam is to be classified as continuous supply, as per examples given in the directive's recitals. I.e. 2a applies and not 2b, meaning the trader shall ensure supply of updates, including security updates, to keep the software in conformity for as long as supply lasts, i.e. for as long as the consumer's Steam account continues to have access to the game to install and play it. Reasonably expectations wrt such things as end-of-support and end-of-life only apply to the case of 2b; not 2a.
(This is logical in a sense: how can something still be in active supply, yet be end-of-life?)
Btw, chrunchyfrog, looping back to your request for the relevant clause that says security vulnerabilities apply: this is another relevant passage where security updates are explicitly mentioned as a requirement the trader shall ensure for.
No need to call for drama.