Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.

User talk:Cyanic/Steam DRM

About this board

Not editable


Link from Digital rights management (DRM)#Steam/Steamworks to here

2
Aemony (talkcontribs)

I've added a link from the general DRM page to this user page of yours for those looking for more in-depth information about the DRM variants of Steam. I hope you're fine with this, otherwise I will remove the link and investigate alternative solutions.

Kudos for creating this article to begin with.

Cyanic (talkcontribs)

Not sure what was previously listed for Steamworks, but Steam DRM is actually tangential. Although a good number of games use the DRM wrapper, most games require the API to be working to actually function, which is where its DRM-like behavior comes from. So you should probably list Steamworks API as the primary DRM, then this wrapper as a secondary DRM Valve has made available.

Kobi Blade (talkcontribs)

SteamStub is not the Steam DRM, you guys were spreading misinformation all this time.

In fact SteamStub is a feature of the SteamAPI (DRM), that is rarely used to encrypt game files, when removing the SteamStub you leave the game files vulnerable to exploits (Cracks).

Nowadays scene groups simply emulate the SteamAPI and be done with it.

Cyanic (talkcontribs)

Sorry, didn't notice this comment earlier. I'm not seeing which part is misinformation. Steam DRM is the official name given to this particular scheme, as you can see at https://partner.steamgames.com/doc/features/drm. SteamStub is a common name given to this scheme by scene groups. I don't think I've claimed that it encrypts game files other than the main EXE. API emulation is a different matter, and can't be relied on solely to bypass the wrapper's authentication as the wrapper also verifies app tickets, which are signed using public-key cryptography.

Cyanic (talkcontribs)

While the Steamworks FAQ states that Adobe AIR games cannot be wrapped, in reality that doesn't seem to be true. I test wrapped an Adobe AIR game and it worked perfectly fine. What I think they meant was games that use overlays may have problems finding the overlay depending on its search method. All overlay data is put into the .extra section and included as a part of the PE image in v2. If a game assumes the overlay starts at the end of the PE image or begins its search there, it will surely not find it. For programs that search the entire file, they should be OK as long as DRM components do not happen to match whatever is being searched for. For v3, overlay is completely truncated (for whatever reason), and any game that uses an overlay won't be able to run if wrapped with v3.

Note: "overlay" in this context is defined as the data that comes after a PE image but is in the same file as the PE image.

There are no older topics