You can sign up to get a daily email of our articles, see the Mailing List page!
Latest Comments by beniwtv
Steam Play thoughts: A Valve game streaming service
1 November 2018 at 4:33 pm UTC

Purple Library GuyI disagree. What you don't own is the copyright. What FOSS software licenses license, set conditions on (or rather, mainly explicitly remove default conditions from), is the copyright. When you buy a game, a copy of the game IS your personal property. You do not hold the copyright so you don't have a right to copy it.
It's true that software companies have been trying hard to make the situation ambiguous and fuzz the law with their EULAs and so forth, but in most countries if it came down to a court case it would turn out that the purchaser of a thing owns it, even if it's a digital thing.

But that's exactly what is said!

You don't own the copyright, you don't own the work. You may own the physical copy the work is on though, but that still does not make you own the work. You own a license to use the work (described in the license / EULA).

And FOSS licenses do not remove copyright. They just make some exemptions to it, see:
https://www.gnu.org/licenses/gpl-howto.en.html

Copyright isn't just about "copying" the work.

Steam Play thoughts: A Valve game streaming service
1 November 2018 at 3:25 pm UTC

My thoughts on DRM/Cloud gaming/Always-Online games is that personally, I have mixed feelings for those things.

I am myself not the type of gamer that goes and re-plays games once I've played the story once. Even with "recurring" games like Rocket League, there comes a time when I leave them for good, when there's no more interest in playing the same game over and over. So on that side, I don't see myself affected by DRM/Cloud/Always-Online in the sense that I do not care if games are taken away from me once I've played them; I have no interest in them anymore anyway.

HOWEVER, on the other side, I am very much against DRM/Cloud gaming/Always-Online - the reason is that I believe games should be preserved for future generations, or players that have never played them. We can not preserve these games if we're actively being hindered by it.

Worst thing is, the industry does not care about preserving games - they actively go against it even years after the game is no longer being sold. I hope for a world where DRM is stripped from games after it's no longer necessary (or not even put in to begin with!), or small server back-ends/offline patches released for Always-Online games, or cloud streamed games getting a downloadable package once it's no longer offered on the streaming services.

It wouldn't be hard for devs to do these tings, and let the gamer community worry about game preservation.

Steam Play thoughts: A Valve game streaming service
1 November 2018 at 3:13 pm UTC Likes: 4

NanobangI'm no fan of "the" cloud in general as it continues the trend of further eroding control of what otherwise would be one's personal property.

Just quickly want to chime in here: Games/software are not your personal property. You may own a physical medium the game/software is on though, which is your property. But you still need a license to use that copy.

So, games and software are licensed. Even FOSS software. Otherwise, you would own the right to them, which you do not.

I get what you wanted to say here, though. And I agree, when owning a physical copy without DRM probably nobody is gonna bother you in the future, to take it away or prevent you from playing it.

The Steam Beta Client has some updates to the runtime for games that needs testing
26 October 2018 at 2:56 pm UTC

devnullThat is IMPOSSIBLE. The whole reason code uses third party libs for things like SSL (collectively refering to all things "Secure this connection between two points") - is not worrying about it breaking.

Well it's not impossible - but time consuming. A full-time job in itself for many applications. I agree 100% though that security-related libraries should not break API, unless there is REALLY REALLY no other way (or a completely new protocol that can't be represented with the current API).

In fact, any library not breaking API would be nice - but this is hard to do in itself. Sometimes conserving an old API is a great source of hold-back for a library.

I recently linked GnuTLS 3.0 to Proton that was compiled against GnuTLS 2.6, and things do work now, in many games. So I think at least the developers did try to conserve the API as much as possible in this specific case.

The Steam Beta Client has some updates to the runtime for games that needs testing
26 October 2018 at 10:42 am UTC

devnullDepends which bugs you're refering to but they were certainly known, maybe not as public.

I can obviously only speak of public disclosure of these bugs, for example POODLE was disclosed 2014: https://access.redhat.com/articles/1232123

Whether it was known in 2009, I don't know. At least us server admins/app devs did not know until that point.

devnullDo you know how TLS1.3 works? It's not a silver bullet and there was nothing stopping applications from enforcing security policy. I know because it's one of the first things I do on installs.

Agree, no security protocol will ever be perfect - but that doesn't mean we should just leave old broken protocols enabled. Yes you can take steps to mitigate things like POODLE or BEAST, but for example in the case of POODLE both server AND client have to be patched - just ensuring your local app policy is half the work.

Also SSLv3 client applications tend to be older and use weaker ciphers.

devnullI don't follow this at all for the simple fact I updated libgnutls to my own distro's "latest", and STILL have problems. While the steam runtime may be old, requiring bleeding edge rolling releases is ... assinine.

The issue with COMPILING TLS have NOTHING to do with Steam. What on Earth. Do you know what other dependencies that involves?

I have no idea what your distro's latest version is, so can't comment on that. It is of course possible GnuTLS has bugs of it's own making connections fail.

I don't think understand you last sentence - as an app dev you ARE responsible of keeping your dependencies up to date. Steam-runtime or not. Problem is, if developers only target the runtime, they will get outdated dependencies.

The Steam Beta Client has some updates to the runtime for games that needs testing
26 October 2018 at 8:34 am UTC

devnullQuite frankly I'm at the point of blaming networks for turning off older TLS with no fallback.

The fallback is called "newer TLS version", and has been supported by OSes and applications for quite a while. Obviously old GnuTLS didn't support them. GnuTLS 2.6.6 was released on 2009-04-30, more than 9 years ago. We did not even know about the vulnerabilities back then.

Blaming networks for caring about your data's security and disabling these broken protocols seems a bit odd.

The issue here isn't GnuTLS or the networks, but the Steam runtime being so old and not being kept up to date (at least the security relevant parts of it should be updated).

The Steam Beta Client has some updates to the runtime for games that needs testing
24 October 2018 at 12:41 pm UTC

Wernerhttps://github.com/ValveSoftware/steam-runtime/issues/101

maybe related to this, users reported issues with uplay to name one

https://github.com/ValveSoftware/Proton/issues/1789

That's my assumption too. The version of GnuTLS used by the Steam runtime/Proton is becoming so old that going forward all TLS connections will cease to work, as the old protocols have security issues and are being deprecated.

Valve just put out another (smaller) Steam Play beta version
23 October 2018 at 12:20 pm UTC

Sil_el_motBUdget Cuts works fine for you? You tested it some levels or just the very entry of the game? I don't see any robots when i try to start the game and comparing it with the spcr.netlify.com-database i am not the only one.

I'll have to check again, I'm not sure now.

Valve just put out another (smaller) Steam Play beta version
19 October 2018 at 7:54 am UTC

coolboberLinks:
sudo ln -s /usr/lib/i386-linux-gnu/libgnutls.so.30.14.10 /usr/lib/i386-linux-gnu/libgnutls.so.26
and
sudo ln -s /usr/lib/x86_64-linux-gnu/i386-linux-gnu/libgnutls.so.30.14.10 /usr/lib/x86_64-linux-gnu/libgnutls.so.26

Those do look right. Only other thing(s) comes to mind:

1) Somehow that game isn't using the Proton 3.16-3 beta version (check in Steam Play settings, maybe you need to set "Use this version instead of a game-specific version).

2) There might be another libgnutls.so.26 in Proton's/Steams? lib/ directory, or somewhere else on the system and it gets picked up first

Valve just put out another (smaller) Steam Play beta version
18 October 2018 at 2:42 pm UTC

coolboberThanks but still no luck for me...

Sorry to hear that. What links have you currently set?

  Go to:
Livestreams & Videos
Community Livestreams
  • Story Time: „Ankh 2: Heart of Osiris“ (via Proton)
  • Date:
See more!
Popular this week
View by Category
Contact
Latest Comments
Latest Forum Posts