mirror of https://github.com/libsdl-org/SDL.git synced 2026-02-28 22:28:19 +00:00

Files

Simon McVittie 888104f5ad Document SDL's policy on setuid/setgid executables

Stated briefly, the policy is: don't.

Resolves: https://github.com/libsdl-org/SDL/issues/14717
Signed-off-by: Simon McVittie <smcv@debian.org>
(cherry picked from commit 76352f2931)

2025-12-28 10:16:44 -08:00

1.7 KiB

Raw Blame History

Platforms

Supported Platforms

Unsupported Platforms

If your favorite system is listed below, we aren't working on it. However, if you send reasonable patches and are willing to support the port in the long term, we are happy to take a look!

All of these still work with SDL2, which is an incompatible API, but an option if you need to support these platforms still.

Google Stadia
NaCL
Nokia N-Gage
OS/2
QNX
WinPhone
WinRT/UWP

General notes for Unix platforms

Some aspects of SDL functionality are common to all Unix-based platforms.

Privileged processes (setuid, setgid, setcap)

SDL is not designed to be used in programs with elevated privileges, such as setuid (chmod u+s) or setgid (chmod g+s) executables, or executables with file-based capabilities (setcap cap_sys_nice+ep or similar). It does not make any attempt to avoid trusting environment variables or other aspects of the inherited execution environment. Programs running with elevated privileges in an attacker-controlled execution environment should not call SDL functions.

1.7 KiB Raw Blame History