Injecting DLLs into the steam client

[UZ]

Doesn't editing the steam clients dynamic link libraries trigger vac bans?, or is it just for video games only

[Cathulhu]

VAC only covers games. But depending on what you are trying to achieve you could trigger other safeguards and get your account suspended.

[UZ]

Originally posted by Cathulhu:

VAC only covers games. But depending on what you are trying to achieve you could trigger other safeguards and get your account suspended.

What are some of these safeguards?

[Wolf Knight]

Originally posted by UZ:

Originally posted by Cathulhu:

VAC only covers games. But depending on what you are trying to achieve you could trigger other safeguards and get your account suspended.

What are some of these safeguards?

community ban, account locked, account TERMINATED, etc

[metamec]

It is quite possible. I would be more bothered about the potential for an unsigned dll to be malware, considering (simplifying a bit) dll files are essentially exe files without entry points.

Ie. They can contain exactly the same low level, potentially system compromising code, but the functions have to be exported and called by a separate exe process (in this case, Steam) or something like rundll32.exe. I won't let them anywhere near my system unless I can evaluate and compile the source myself. Consequently I have to reject most mods.

[Satoru]

If you leave whatever is trying to inject into the dll running, its entirely possible to trigger a game ban or vac ban.

[KnnyWT]

Yeah

[Crashed]

Originally posted by UZ:

Doesn't editing the steam clients dynamic link libraries trigger vac bans?, or is it just for video games only

Depends on what DLL is injected and whether or not it tampers with the client or any running game files.

There are DLLs that inject themselves into all running processes, or all processes that use a particular API, and Valve won't ban you for things that don't specifically target any sensitive components of the Steam Client.